@keystrokehq/spondyr 0.1.2 → 0.1.3

package/dist/actions/transaction-type-update.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"transaction-type-update.mjs","names":[],"sources":["../../src/actions/transaction-type-update.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const SpondyrTransactionTypeUpdateInput = z.object({\n  Name: z.string().describe(\"The new or updated name for the transaction type. Use the same value as TransactionType to keep the name unchanged, or provide a different value to rename it.\"),\n  TemplateJSON: z.string().describe(\"A valid JSON-formatted string defining the transaction schema with all available properties and sample data. This defines what data fields are available for correspondence templates.\"),\n  TransactionType: z.string().describe(\"The name of the existing transaction type to update. This identifies which transaction type to modify.\"),\n});\nexport const SpondyrTransactionTypeUpdateOutput = z.object({\n  APIStatus: z.enum([\"OK\", \"ERROR\"]).describe(\"Status of the API request. 'OK' indicates the transaction type was successfully updated, 'ERROR' indicates a failure.\").nullable(),\n  ReferenceID: z.string().describe(\"Unique identifier for the updated transaction type. Use this ID for subsequent operations like retrieving or further updating the transaction type.\").nullable(),\n  ErrorMessage: z.string().describe(\"Detailed error message explaining why the update failed. Only present when APIStatus is 'ERROR'.\").nullable().optional(),\n});\n\nexport const spondyrTransactionTypeUpdate = action(\"SPONDYR_TRANSACTION_TYPE_UPDATE\", {\n  slug: \"spondyr-transaction-type-update\",\n  name: \"Update Transaction Type\",\n  description: \"Updates an existing transaction type's name and/or JSON schema in Spondyr. Use this tool to: - Modify the JSON schema/template of a transaction type to add, remove, or change data fields - Rename an existing transaction type - Update sample data values in the template Prerequisites: The transaction type must already exist. Use 'Get Transaction Types' to list available types or 'Get Transaction Type' to retrieve the current schema before updating. Example: Update the 'OrderPlaced' transaction type with a new JSON schema that includes customer address fields.\",\n  input: SpondyrTransactionTypeUpdateInput,\n  output: SpondyrTransactionTypeUpdateOutput,\n});\n"],"mappings":";;AAeA,MAAa,+BAA+B,OAAO,mCAAmC;CACpF,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAf+C,EAAE,OAAO;EACxD,MAAM,EAAE,OAAO,CAAC,CAAC,SAAS,gKAAgK;EAC1L,cAAc,EAAE,OAAO,CAAC,CAAC,SAAS,wLAAwL;EAC1N,iBAAiB,EAAE,OAAO,CAAC,CAAC,SAAS,wGAAwG;CAC/I,CAWS;CACP,QAXgD,EAAE,OAAO;EACzD,WAAW,EAAE,KAAK,CAAC,MAAM,OAAO,CAAC,CAAC,CAAC,SAAS,uHAAuH,CAAC,CAAC,SAAS;EAC9K,aAAa,EAAE,OAAO,CAAC,CAAC,SAAS,qJAAqJ,CAAC,CAAC,SAAS;EACjM,cAAc,EAAE,OAAO,CAAC,CAAC,SAAS,kGAAkG,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC5J,CAOU;AACV,CAAC"}
+{"version":3,"file":"transaction-type-update.mjs","names":[],"sources":["../../src/actions/transaction-type-update.ts"],"sourcesContent":["import { z } from \"zod\";\n\nimport { action } from \"../action\";\n\nexport const SpondyrTransactionTypeUpdateInput = z.object({\n  Name: z.string().describe(\"The new or updated name for the transaction type. Use the same value as TransactionType to keep the name unchanged, or provide a different value to rename it.\"),\n  TemplateJSON: z.string().describe(\"A valid JSON-formatted string defining the transaction schema with all available properties and sample data. This defines what data fields are available for correspondence templates.\"),\n  TransactionType: z.string().describe(\"The name of the existing transaction type to update. This identifies which transaction type to modify.\"),\n});\nexport const SpondyrTransactionTypeUpdateOutput = z.object({\n  APIStatus: z.enum([\"OK\", \"ERROR\"]).describe(\"Status of the API request. 'OK' indicates the transaction type was successfully updated, 'ERROR' indicates a failure.\").nullable(),\n  ReferenceID: z.string().describe(\"Unique identifier for the updated transaction type. Use this ID for subsequent operations like retrieving or further updating the transaction type.\").nullable(),\n  ErrorMessage: z.string().describe(\"Detailed error message explaining why the update failed. Only present when APIStatus is 'ERROR'.\").nullable().optional(),\n}).passthrough();\n\nexport const spondyrTransactionTypeUpdate = action(\"SPONDYR_TRANSACTION_TYPE_UPDATE\", {\n  slug: \"spondyr-transaction-type-update\",\n  name: \"Update Transaction Type\",\n  description: \"Updates an existing transaction type's name and/or JSON schema in Spondyr. Use this tool to: - Modify the JSON schema/template of a transaction type to add, remove, or change data fields - Rename an existing transaction type - Update sample data values in the template Prerequisites: The transaction type must already exist. Use 'Get Transaction Types' to list available types or 'Get Transaction Type' to retrieve the current schema before updating. Example: Update the 'OrderPlaced' transaction type with a new JSON schema that includes customer address fields.\",\n  input: SpondyrTransactionTypeUpdateInput,\n  output: SpondyrTransactionTypeUpdateOutput,\n});\n"],"mappings":";;AAeA,MAAa,+BAA+B,OAAO,mCAAmC;CACpF,MAAM;CACN,MAAM;CACN,aAAa;CACb,OAf+C,EAAE,OAAO;EACxD,MAAM,EAAE,OAAO,CAAC,CAAC,SAAS,gKAAgK;EAC1L,cAAc,EAAE,OAAO,CAAC,CAAC,SAAS,wLAAwL;EAC1N,iBAAiB,EAAE,OAAO,CAAC,CAAC,SAAS,wGAAwG;CAC/I,CAWS;CACP,QAXgD,EAAE,OAAO;EACzD,WAAW,EAAE,KAAK,CAAC,MAAM,OAAO,CAAC,CAAC,CAAC,SAAS,uHAAuH,CAAC,CAAC,SAAS;EAC9K,aAAa,EAAE,OAAO,CAAC,CAAC,SAAS,qJAAqJ,CAAC,CAAC,SAAS;EACjM,cAAc,EAAE,OAAO,CAAC,CAAC,SAAS,kGAAkG,CAAC,CAAC,SAAS,CAAC,CAAC,SAAS;CAC5J,CAAC,CAAC,CAAC,YAOO;AACV,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@keystrokehq/spondyr",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "publishConfig": {
     "access": "public",
     "registry": "https://registry.npmjs.org"