@wix/auto_sdk_stores_customizations-v-3 1.0.85 → 1.0.87
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/build/cjs/index.js.map +1 -1
- package/build/cjs/index.typings.d.ts +5 -8
- package/build/cjs/index.typings.js.map +1 -1
- package/build/cjs/meta.d.ts +4 -7
- package/build/cjs/meta.js.map +1 -1
- package/build/cjs/schemas.js +20 -20
- package/build/cjs/schemas.js.map +1 -1
- package/build/es/index.mjs.map +1 -1
- package/build/es/index.typings.d.mts +5 -8
- package/build/es/index.typings.mjs.map +1 -1
- package/build/es/meta.d.mts +4 -7
- package/build/es/meta.mjs.map +1 -1
- package/build/es/schemas.mjs +20 -20
- package/build/es/schemas.mjs.map +1 -1
- package/build/internal/cjs/index.js.map +1 -1
- package/build/internal/cjs/index.typings.d.ts +5 -8
- package/build/internal/cjs/index.typings.js.map +1 -1
- package/build/internal/cjs/meta.d.ts +4 -7
- package/build/internal/cjs/meta.js.map +1 -1
- package/build/internal/cjs/schemas.js +20 -20
- package/build/internal/cjs/schemas.js.map +1 -1
- package/build/internal/es/index.mjs.map +1 -1
- package/build/internal/es/index.typings.d.mts +5 -8
- package/build/internal/es/index.typings.mjs.map +1 -1
- package/build/internal/es/meta.d.mts +4 -7
- package/build/internal/es/meta.mjs.map +1 -1
- package/build/internal/es/schemas.mjs +20 -20
- package/build/internal/es/schemas.mjs.map +1 -1
- package/package.json +2 -2
|
@@ -194,8 +194,8 @@ interface Choice extends ChoiceValueOneOf {
|
|
|
194
194
|
*/
|
|
195
195
|
defaultAddedPrice?: string | null;
|
|
196
196
|
/**
|
|
197
|
-
* Optional image displayed alongside a ONE_COLOR choice in the storefront.
|
|
198
|
-
* Only valid for ONE_COLOR choices; not populated for other choice types.
|
|
197
|
+
* Optional image displayed alongside a `ONE_COLOR` choice in the storefront.
|
|
198
|
+
* Only valid for `ONE_COLOR` choices; not populated for other choice types.
|
|
199
199
|
*/
|
|
200
200
|
displayImage?: string;
|
|
201
201
|
/**
|
|
@@ -443,10 +443,7 @@ interface GetCustomizationRequest {
|
|
|
443
443
|
declare enum RequestedFields {
|
|
444
444
|
/** Assigned products count. */
|
|
445
445
|
ASSIGNED_PRODUCTS_COUNT = "ASSIGNED_PRODUCTS_COUNT",
|
|
446
|
-
/**
|
|
447
|
-
* Returns display images for choices.
|
|
448
|
-
* @documentationMaturity preview
|
|
449
|
-
*/
|
|
446
|
+
/** Returns display images for choices. */
|
|
450
447
|
CHOICE_DISPLAY_IMAGE = "CHOICE_DISPLAY_IMAGE"
|
|
451
448
|
}
|
|
452
449
|
/** @enumType */
|
|
@@ -939,7 +936,7 @@ interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
939
936
|
/** If present, indicates the action that triggered the event. */
|
|
940
937
|
originatedFrom?: string | null;
|
|
941
938
|
/**
|
|
942
|
-
* A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at 16:00 and then again at 16:01
|
|
939
|
+
* A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at `16:00` and then again at `16:01`, the second update will always have a higher sequence number.
|
|
943
940
|
* You can use this number to make sure you're handling updates in the right order. Just save the latest sequence number on your end and compare it to the one in each new message. If the new message has an older (lower) number, you can safely ignore it.
|
|
944
941
|
*/
|
|
945
942
|
entityEventSequence?: string | null;
|
|
@@ -1315,7 +1312,7 @@ interface EventMetadata extends BaseEventMetadata {
|
|
|
1315
1312
|
/** If present, indicates the action that triggered the event. */
|
|
1316
1313
|
originatedFrom?: string | null;
|
|
1317
1314
|
/**
|
|
1318
|
-
* A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at 16:00 and then again at 16:01
|
|
1315
|
+
* A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at `16:00` and then again at `16:01`, the second update will always have a higher sequence number.
|
|
1319
1316
|
* You can use this number to make sure you're handling updates in the right order. Just save the latest sequence number on your end and compare it to the one in each new message. If the new message has an older (lower) number, you can safely ignore it.
|
|
1320
1317
|
*/
|
|
1321
1318
|
entityEventSequence?: string | null;
|