dataconv-client-sdk-ts 0.2.0 → 0.2.1

package/README.md

@@ -41,7 +41,6 @@ import { DataConvClient } from 'dataconv-client-sdk-ts';
 
 const client = new DataConvClient({
   issuerDid: 'did:web:clinic.example:employee:...',
-  alternateName: 'clinic-demo',
   tenantId: 'VATES-B00000000',
   jurisdiction: 'ES',
   sector: 'onehealth-research',
@@ -144,7 +143,6 @@ const httpClient = axios.create({
 
 const client = new DataConvClient({
   issuerDid: activatedOrganizationDid,
-  alternateName: tenantAlternateName,
   tenantId: tenantAlternateName,
   jurisdiction: 'ES',
   httpClient,
@@ -159,7 +157,6 @@ It also works with `fetch`:
 ```ts
 const client = new DataConvClient({
   issuerDid: activatedOrganizationDid,
-  alternateName: tenantAlternateName,
   tenantId: tenantAlternateName,
   jurisdiction: 'ES',
   fetch,
@@ -169,7 +166,7 @@ const client = new DataConvClient({
 
 ## Notes
 
-- For configuration and conversion calls, the operational tenant identifier should be `tenantId`, typically the organization's VAT/taxId. `alternateName` remains as a compatibility alias.
+- For configuration and conversion calls, the operational tenant identifier should be `tenantId`, typically the organization's VAT/taxId.
 - `sector` is variable and is part of the public route for config, digital twin, and search.
 - `patchConversion()` defaults to `Composition/_patch`.
 - `batchPromotion()` defaults to `Patient/_batch`.

package/package.json

@@ -1,10 +1,15 @@
 {
   "name": "dataconv-client-sdk-ts",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "TypeScript SDK for adapter-ingestion-py preconversion APIs via DIDComm and multipart upload.",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
+  "files": [
+    "dist",
+    "README.md",
+    "LICENSE"
+  ],
   "scripts": {
     "build": "tsc",
     "test": "DATACONV_BASE_URL=http://localhost:8080 jest",

package/.github/copilot-instructions.md

@@ -1,104 +0,0 @@
-<!-- Use this file to provide workspace-specific custom instructions to Copilot. For more details, visit https://code.visualstudio.com/docs/copilot/copilot-customization#_use-a-githubcopilotinstructionsmd-file -->
-- [x] Verify that the copilot-instructions.md file in the .github directory is created.
-
-- [x] Clarify Project Requirements
-	<!-- Ask for project type, language, and frameworks if not specified. Skip if already provided. -->
-
-- [x] Scaffold the Project
-	<!--
-	Ensure that the previous step has been marked as completed.
-	Call project setup tool with projectType parameter.
-	Run scaffolding command to create project files and folders.
-	Use '.' as the working directory.
-	If no appropriate projectType is available, search documentation using available tools.
-	Otherwise, create the project structure manually using available file creation tools.
-	-->
-
-- [x] Customize the Project
-	<!--
-	Verify that all previous steps have been completed successfully and you have marked the step as completed.
-	Develop a plan to modify codebase according to user requirements.
-	Apply modifications using appropriate tools and user-provided references.
-	Skip this step for "Hello World" projects.
-	-->
-
-- [ ] Install Required Extensions
-	<!-- ONLY install extensions provided mentioned in the get_project_setup_info. Skip this step otherwise and mark as completed. -->
-
-- [x] Compile the Project
-	<!--
-	Verify that all previous steps have been completed.
-	Install any missing dependencies.
-	Run diagnostics and resolve any issues.
-	Check for markdown files in project folder for relevant instructions on how to do this.
-	-->
-
-- [ ] Create and Run Task
-	<!--
-	Verify that all previous steps have been completed.
-	Check https://code.visualstudio.com/docs/debugtest/tasks to determine if the project needs a task. If so, use the create_and_run_task to create and launch a task based on package.json, README.md, and project structure.
-	Skip this step otherwise.
-	 -->
-
-- [ ] Launch the Project
-	<!--
-	Verify that all previous steps have been completed.
-	Prompt user for debug mode, launch only if confirmed.
-	 -->
-
-- [x] Ensure Documentation is Complete
-	<!--
-	Verify that all previous steps have been completed.
-	Verify that README.md and the copilot-instructions.md file in the .github directory exists and contains current project information.
-	Clean up the copilot-instructions.md file in the .github directory by removing all HTML comments.
-	 -->
-
-<!--
-## Execution Guidelines
-PROGRESS TRACKING:
-- If any tools are available to manage the above todo list, use it to track progress through this checklist.
-- After completing each step, mark it complete and add a summary.
-- Read current todo list status before starting each new step.
-
-COMMUNICATION RULES:
-- Avoid verbose explanations or printing full command outputs.
-- If a step is skipped, state that briefly (e.g. "No extensions needed").
-- Do not explain project structure unless asked.
-- Keep explanations concise and focused.
-
-DEVELOPMENT RULES:
-- Use '.' as the working directory unless user specifies otherwise.
-- Avoid adding media or external links unless explicitly requested.
-- Use placeholders only with a note that they should be replaced.
-- Use VS Code API tool only for VS Code extension projects.
-- Once the project is created, it is already opened in Visual Studio Code—do not suggest commands to open this project in vscode.
-- If the project setup information has additional rules, follow them strictly.
-
-FOLDER CREATION RULES:
-- Always use the current directory as the project root.
-- If you are running any terminal commands, use the '.' argument to ensure that the current working directory is used ALWAYS.
-- Do not create a new folder unless the user explicitly requests it besides a .vscode folder for a tasks.json file.
-- If any of the scaffolding commands mention that the folder name is not correct, let the user know to create a new folder with the correct name and then reopen it again in vscode.
-
-EXTENSION INSTALLATION RULES:
-- Only install extension specified by the get_project_setup_info tool. DO NOT INSTALL any other extensions.
-
-PROJECT CONTENT RULES:
-- If the user has not specified project details, assume they want a "Hello World" project as a starting point.
-- Avoid adding links of any type (URLs, files, folders, etc.) or integrations that are not explicitly required.
-- Avoid generating images, videos, or any other media files unless explicitly requested.
-- If a feature is assumed but not confirmed, prompt the user for clarification before including it.
-- If you are working on a VS Code extension, use the VS Code API tool with a query to find relevant VS Code API references and samples related to that query.
-
-TASK COMPLETION RULES:
-- Your task is complete when:
-  - Project is successfully scaffolded and compiled without errors
-  - copilot-instructions.md file in the .github directory exists
-  - README.md file exists and is up to date
-  - User is provided with clear instructions to debug/launch the project
-
-Before starting a new task in the above plan, update progress in the plan.
--->
-- Work through each checklist item systematically.
-- Keep communication concise and focused.
-- Follow development best practices.

package/__mocks__/gdc-common-utils-ts/utils/didcomm.ts

@@ -1,39 +0,0 @@
-export class DidCommMessage {
-  id = 'mock';
-  type = '';
-  body: any = {};
-  attachments?: any[];
-  thid?: string;
-}
-
-export type DidCommAttachment = {
-  id: string;
-  media_type: string;
-  data: any;
-};
-
-export function prepareDidCommRequest(type: string, body: any = {}, attachments: any[] = []): DidCommMessage {
-  const message = new DidCommMessage();
-  message.type = type;
-  message.body = body;
-  message.attachments = attachments;
-  message.thid = message.id;
-  return message;
-}
-
-export function includeVpTokenInMessage(message: DidCommMessage, vpToken: string): void {
-  message.body.vp_token = vpToken;
-}
-
-export function includeFileInMessage(message: DidCommMessage, fileBytes: Uint8Array, mediaType: string, id: string): void {
-  if (!message.attachments) message.attachments = [];
-  message.attachments.push({ id, media_type: mediaType, data: { base64: Buffer.from(fileBytes).toString('base64') } });
-}
-
-export function getThidFromMessage(message: DidCommMessage): string {
-  return message.thid || message.id;
-}
-
-export function getDataResults(response: DidCommMessage): any[] {
-  return response.body?.data || [];
-}

package/jest.config.js

@@ -1,16 +0,0 @@
-/** @type {import('ts-jest').JestConfigWithTsJest} */
-export default {
-  preset: 'ts-jest/presets/default-esm',
-  testEnvironment: 'node',
-  extensionsToTreatAsEsm: ['.ts'],
-  moduleNameMapper: {
-    '^(\\.{1,2}/.*)\\.js$': '$1'
-  },
-  globals: {
-    'ts-jest': {
-      tsconfig: 'tsconfig.json',
-      useESM: true
-    }
-  },
-  transformIgnorePatterns: ['/node_modules/(?!gdc-common-utils-ts)'],
-};