@viu/emporix-sdk 4.2.0 → 4.2.3

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @viu/emporix-sdk
 
+## 4.2.3
+
+### Patch Changes
+
+- [#374](https://github.com/viuteam/emporix-sdk/pull/374) [`3418d90`](https://github.com/viuteam/emporix-sdk/commit/3418d9066fa2f9f1ec83a0499f1fa365cbee21b0) Thanks [@viu-release-bot](https://github.com/apps/viu-release-bot)! - chore(sdk): sync generated types with upstream Emporix API specs
+  
+  Updated services: ai-rag-indexer,ai-service,approval-service,audit-logs-changelog,availability,cart,category,checkout,customer,customer-segment,customer-service,import-service,indexing-service,label-service,order-v2,price,product,sequential-id,session-context,shopping-list
+
+## 4.2.2
+
+### Patch Changes
+
+- [#372](https://github.com/viuteam/emporix-sdk/pull/372) [`b89a81a`](https://github.com/viuteam/emporix-sdk/commit/b89a81a9eed1cdbf781757d5e5f09820f6cb04af) Thanks [@amnael1](https://github.com/amnael1)! - docs(sdk): document published mappings and aborted import runs
+  
+  The import types and `triggerRun` / `retryRun` now describe the Import Service change of 2026-09-28, which the types already carried: a run executes each stream's published mappings, a dry run checks the drafts with `mappings: "draft"`, and runs report `mappingVersions` and `dryRunPublished`. They also name the trap that came with it — a run refused for never-published mappings still resolves with `200` and only then finishes `ABORTED`, so read the run back before treating it as started.
+
 ## 4.2.0
 
 ### Minor Changes

package/dist/cart.d.cts

@@ -21,7 +21,7 @@ type Search = {
     /**
      * A standard query parameter is used to search for specific values.
      *
-     * See: [Standard practises - Query parameter](https://developer.emporix.io/api-references/standard-practices/q-param/)
+     * See: [Standard Practices - Query parameter](https://developer.emporix.io/api-documentation/standard-practices/q-param)
      *
      */
     q?: string;
@@ -76,7 +76,7 @@ type BaseCart = {
      * * If the cart has a legal entity, it gets the first location of the legal entity that has both `country` and `zipCode`, and matches the required `type` - then the address has origin=`LEGAL_ENTITY`.
      * * Otherwise, if the cart has a logged-in customer, it finds the `default` address that has both `country` and `zipCode`, and matches the required `type`. If there is no matching default address with the required information, it uses the first customer address that meets the criteria. The address has origin=`CUSTOMER`.
      * * Otherwise, the cart uses the site homebase address. Then the address has origin=`SITE`.
-     * These addresses are used in the tax country code determination [How to determine a tax country at cart level](https://developer.emporix.io/api-references/api-guides/checkout/cart/cart#how-to-determine-a-tax-country-at-cart-level) and shipping cost calculation [How to calculate shipping cost at cart level](https://developer.emporix.io/api-references/api-guides/checkout/cart/cart#how-to-calculate-shipping-cost-at-cart-level).
+     * These addresses are used in the tax country code determination [How to determine a tax country at cart level](https://developer.emporix.io/api-documentation/api-guides/checkout/cart/cart#how-to-determine-a-tax-country-at-cart-level) and shipping cost calculation [How to calculate shipping cost at cart level](https://developer.emporix.io/api-documentation/api-guides/checkout/cart/cart#how-to-calculate-shipping-cost-at-cart-level).
      */
     addresses?: Array<AddressResponse>;
     channel?: Channel;

package/dist/cart.d.ts

@@ -21,7 +21,7 @@ type Search = {
     /**
      * A standard query parameter is used to search for specific values.
      *
-     * See: [Standard practises - Query parameter](https://developer.emporix.io/api-references/standard-practices/q-param/)
+     * See: [Standard Practices - Query parameter](https://developer.emporix.io/api-documentation/standard-practices/q-param)
      *
      */
     q?: string;
@@ -76,7 +76,7 @@ type BaseCart = {
      * * If the cart has a legal entity, it gets the first location of the legal entity that has both `country` and `zipCode`, and matches the required `type` - then the address has origin=`LEGAL_ENTITY`.
      * * Otherwise, if the cart has a logged-in customer, it finds the `default` address that has both `country` and `zipCode`, and matches the required `type`. If there is no matching default address with the required information, it uses the first customer address that meets the criteria. The address has origin=`CUSTOMER`.
      * * Otherwise, the cart uses the site homebase address. Then the address has origin=`SITE`.
-     * These addresses are used in the tax country code determination [How to determine a tax country at cart level](https://developer.emporix.io/api-references/api-guides/checkout/cart/cart#how-to-determine-a-tax-country-at-cart-level) and shipping cost calculation [How to calculate shipping cost at cart level](https://developer.emporix.io/api-references/api-guides/checkout/cart/cart#how-to-calculate-shipping-cost-at-cart-level).
+     * These addresses are used in the tax country code determination [How to determine a tax country at cart level](https://developer.emporix.io/api-documentation/api-guides/checkout/cart/cart#how-to-determine-a-tax-country-at-cart-level) and shipping cost calculation [How to calculate shipping cost at cart level](https://developer.emporix.io/api-documentation/api-guides/checkout/cart/cart#how-to-calculate-shipping-cost-at-cart-level).
      */
     addresses?: Array<AddressResponse>;
     channel?: Channel;

package/dist/checkout.d.cts

@@ -156,7 +156,7 @@ type RequestFromQuoteCheckout = {
 type RequestPaymentMethodJson = {
     /**
      * Payment provider, possible values:
-     * * `payment-gateway` - When the Emporix Payment-Gateway service should be used to handle a payment. For details about custom attributes that are required for a particular payment mode, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments.
+     * * `payment-gateway` - When the Emporix Payment-Gateway service is used to handle a payment. For details about custom attributes that are required for a particular payment mode, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway.
      * * `custom` - When a custom provider is used. In this case the created order has the `IN_CHECKOUT` status.
      * * `none` - For payment by cash or invoice.
      *
@@ -167,11 +167,11 @@ type RequestPaymentMethodJson = {
      */
     customAttributes?: {
         /**
-         * Payment token used for the tokenized credit card flows. The field is used when provider type is `payment-gateway`. For more details, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments
+         * Payment token used for the tokenized credit card flows. The field is used when provider type is `payment-gateway`. For more details, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway
          */
         token?: string;
         /**
-         * Identifier of a payment mode. The payment mode has to be configured in the Emporix Payment Gateway service beforehand. For more details, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments
+         * Identifier of a payment mode. The payment mode has to be configured in the Emporix Payment Gateway service beforehand. For more details, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway
          */
         modeId?: string;
         /**

package/dist/checkout.d.ts

@@ -156,7 +156,7 @@ type RequestFromQuoteCheckout = {
 type RequestPaymentMethodJson = {
     /**
      * Payment provider, possible values:
-     * * `payment-gateway` - When the Emporix Payment-Gateway service should be used to handle a payment. For details about custom attributes that are required for a particular payment mode, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments.
+     * * `payment-gateway` - When the Emporix Payment-Gateway service is used to handle a payment. For details about custom attributes that are required for a particular payment mode, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway.
      * * `custom` - When a custom provider is used. In this case the created order has the `IN_CHECKOUT` status.
      * * `none` - For payment by cash or invoice.
      *
@@ -167,11 +167,11 @@ type RequestPaymentMethodJson = {
      */
     customAttributes?: {
         /**
-         * Payment token used for the tokenized credit card flows. The field is used when provider type is `payment-gateway`. For more details, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments
+         * Payment token used for the tokenized credit card flows. The field is used when provider type is `payment-gateway`. For more details, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway
          */
         token?: string;
         /**
-         * Identifier of a payment mode. The payment mode has to be configured in the Emporix Payment Gateway service beforehand. For more details, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments
+         * Identifier of a payment mode. The payment mode has to be configured in the Emporix Payment Gateway service beforehand. For more details, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway
          */
         modeId?: string;
         /**

package/dist/index.cjs

@@ -1242,7 +1242,7 @@ var HttpClient = class {
 };
 
 // package.json
-var version = "4.2.0";
+var version = "4.2.3";
 
 // src/version.ts
 var SDK_VERSION = version;
@@ -8577,6 +8577,19 @@ var ImportService = class {
    * `streamIds` runs a subset — see {@link ImportRunInput} for what is rejected,
    * and note it takes ids where {@link getStreamOrder} reports names.
    *
+   * A run executes each stream's **published** mappings. Publishing needs
+   * `importtool.import_manage` and is not part of the public API, so it happens
+   * in the Management Dashboard's Import Tool rather than through this SDK; a dry
+   * run with `mappings: "draft"` checks unpublished changes first. A stream whose
+   * mappings were never published is `ABORTED` in the run details, and the run
+   * finishes `PARTIAL`.
+   *
+   * **A refused run still resolves.** When `streamIds` names such a stream, or
+   * every enabled stream is in that state, the service answers `200` with the
+   * run anyway, and the run then finishes `ABORTED` with a `message` naming the
+   * streams. Read it back with {@link getRun}, or follow it with
+   * {@link streamRun}, before treating a resolved call as a started import.
+   *
    * Not retried on a 5xx: a POST that timed out may already have queued a run.
    *
    * @example
@@ -8819,7 +8832,8 @@ var ImportService = class {
    *
    * Returns a **new** run — the retry is its own run with `retry: true`, not a
    * mutation of the original. Poll it with {@link getRun} or follow it with
-   * {@link streamRun} exactly as you would a triggered run.
+   * {@link streamRun} exactly as you would a triggered run. Like one, it runs the
+   * published mappings and can finish `ABORTED`.
    *
    * Not retried on a 5xx, for the same reason {@link triggerRun} is not: a POST
    * that timed out may already have queued the retry.