@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
|
@@ -202,8 +202,8 @@ interface Choice extends ChoiceValueOneOf {
|
|
|
202
202
|
*/
|
|
203
203
|
defaultAddedPrice?: string | null;
|
|
204
204
|
/**
|
|
205
|
-
* Optional image displayed alongside a ONE_COLOR choice in the storefront.
|
|
206
|
-
* Only valid for ONE_COLOR choices; not populated for other choice types.
|
|
205
|
+
* Optional image displayed alongside a `ONE_COLOR` choice in the storefront.
|
|
206
|
+
* Only valid for `ONE_COLOR` choices; not populated for other choice types.
|
|
207
207
|
*/
|
|
208
208
|
displayImage?: string;
|
|
209
209
|
/**
|
|
@@ -451,10 +451,7 @@ interface GetCustomizationRequest {
|
|
|
451
451
|
declare enum RequestedFields {
|
|
452
452
|
/** Assigned products count. */
|
|
453
453
|
ASSIGNED_PRODUCTS_COUNT = "ASSIGNED_PRODUCTS_COUNT",
|
|
454
|
-
/**
|
|
455
|
-
* Returns display images for choices.
|
|
456
|
-
* @documentationMaturity preview
|
|
457
|
-
*/
|
|
454
|
+
/** Returns display images for choices. */
|
|
458
455
|
CHOICE_DISPLAY_IMAGE = "CHOICE_DISPLAY_IMAGE"
|
|
459
456
|
}
|
|
460
457
|
/** @enumType */
|
|
@@ -947,7 +944,7 @@ interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
947
944
|
/** If present, indicates the action that triggered the event. */
|
|
948
945
|
originatedFrom?: string | null;
|
|
949
946
|
/**
|
|
950
|
-
* 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
|
|
947
|
+
* 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.
|
|
951
948
|
* 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.
|
|
952
949
|
*/
|
|
953
950
|
entityEventSequence?: string | null;
|
|
@@ -1323,7 +1320,7 @@ interface EventMetadata extends BaseEventMetadata {
|
|
|
1323
1320
|
/** If present, indicates the action that triggered the event. */
|
|
1324
1321
|
originatedFrom?: string | null;
|
|
1325
1322
|
/**
|
|
1326
|
-
* 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
|
|
1323
|
+
* 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.
|
|
1327
1324
|
* 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.
|
|
1328
1325
|
*/
|
|
1329
1326
|
entityEventSequence?: string | null;
|