@wix/auto_sdk_ecom_checkout-settings 1.0.12 → 1.0.14
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/src/ecom-v1-checkout-settings-checkout-settings.types.d.ts +9 -17
- package/build/cjs/src/ecom-v1-checkout-settings-checkout-settings.types.js.map +1 -1
- package/build/cjs/src/ecom-v1-checkout-settings-checkout-settings.universal.d.ts +17 -33
- package/build/cjs/src/ecom-v1-checkout-settings-checkout-settings.universal.js.map +1 -1
- package/build/es/src/ecom-v1-checkout-settings-checkout-settings.types.d.ts +9 -17
- package/build/es/src/ecom-v1-checkout-settings-checkout-settings.types.js.map +1 -1
- package/build/es/src/ecom-v1-checkout-settings-checkout-settings.universal.d.ts +17 -33
- package/build/es/src/ecom-v1-checkout-settings-checkout-settings.universal.js.map +1 -1
- package/build/internal/cjs/src/ecom-v1-checkout-settings-checkout-settings.types.d.ts +9 -17
- package/build/internal/cjs/src/ecom-v1-checkout-settings-checkout-settings.types.js.map +1 -1
- package/build/internal/cjs/src/ecom-v1-checkout-settings-checkout-settings.universal.d.ts +17 -33
- package/build/internal/cjs/src/ecom-v1-checkout-settings-checkout-settings.universal.js.map +1 -1
- package/build/internal/es/src/ecom-v1-checkout-settings-checkout-settings.types.d.ts +9 -17
- package/build/internal/es/src/ecom-v1-checkout-settings-checkout-settings.types.js.map +1 -1
- package/build/internal/es/src/ecom-v1-checkout-settings-checkout-settings.universal.d.ts +17 -33
- package/build/internal/es/src/ecom-v1-checkout-settings-checkout-settings.universal.js.map +1 -1
- package/package.json +3 -3
|
@@ -250,25 +250,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
250
250
|
updatedEvent?: EntityUpdatedEvent;
|
|
251
251
|
deletedEvent?: EntityDeletedEvent;
|
|
252
252
|
actionEvent?: ActionEvent;
|
|
253
|
-
/**
|
|
254
|
-
* Unique event ID.
|
|
255
|
-
* Allows clients to ignore duplicate webhooks.
|
|
256
|
-
*/
|
|
253
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
257
254
|
id?: string;
|
|
258
255
|
/**
|
|
259
|
-
*
|
|
260
|
-
*
|
|
256
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
257
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
261
258
|
*/
|
|
262
259
|
entityFqdn?: string;
|
|
263
260
|
/**
|
|
264
|
-
*
|
|
265
|
-
*
|
|
266
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
261
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
262
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
267
263
|
*/
|
|
268
264
|
slug?: string;
|
|
269
265
|
/** ID of the entity associated with the event. */
|
|
270
266
|
entityId?: string;
|
|
271
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
267
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
272
268
|
eventTime?: Date | null;
|
|
273
269
|
/**
|
|
274
270
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -278,12 +274,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
278
274
|
/** If present, indicates the action that triggered the event. */
|
|
279
275
|
originatedFrom?: string | null;
|
|
280
276
|
/**
|
|
281
|
-
* A sequence number
|
|
282
|
-
*
|
|
283
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
284
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
285
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
286
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
277
|
+
* 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.
|
|
278
|
+
* 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.
|
|
287
279
|
*/
|
|
288
280
|
entityEventSequence?: string | null;
|
|
289
281
|
}
|
|
@@ -311,7 +303,7 @@ export interface EntityUpdatedEvent {
|
|
|
311
303
|
currentEntityAsJson?: string;
|
|
312
304
|
}
|
|
313
305
|
export interface EntityDeletedEvent {
|
|
314
|
-
/** Entity that was deleted */
|
|
306
|
+
/** Entity that was deleted. */
|
|
315
307
|
deletedEntityAsJson?: string | null;
|
|
316
308
|
}
|
|
317
309
|
export interface ActionEvent {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.types.js","sourceRoot":"","sources":["../../../src/ecom-v1-checkout-settings-checkout-settings.types.ts"],"names":[],"mappings":";;;AA4NA,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,wBAAR,QAAQ,QAKnB;AAED,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,yBAAT,SAAS,QAIpB;
|
|
1
|
+
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.types.js","sourceRoot":"","sources":["../../../src/ecom-v1-checkout-settings-checkout-settings.types.ts"],"names":[],"mappings":";;;AA4NA,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,wBAAR,QAAQ,QAKnB;AAED,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,yBAAT,SAAS,QAIpB;AA+KD,IAAY,mBAMX;AAND,WAAY,mBAAmB;IAC7B,0CAAmB,CAAA;IACnB,8DAAuC,CAAA;IACvC,wCAAiB,CAAA;IACjB,4CAAqB,CAAA;IACrB,kCAAW,CAAA;AACb,CAAC,EANW,mBAAmB,mCAAnB,mBAAmB,QAM9B"}
|
|
@@ -228,25 +228,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
228
228
|
updatedEvent?: EntityUpdatedEvent;
|
|
229
229
|
deletedEvent?: EntityDeletedEvent;
|
|
230
230
|
actionEvent?: ActionEvent;
|
|
231
|
-
/**
|
|
232
|
-
* Unique event ID.
|
|
233
|
-
* Allows clients to ignore duplicate webhooks.
|
|
234
|
-
*/
|
|
231
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
235
232
|
_id?: string;
|
|
236
233
|
/**
|
|
237
|
-
*
|
|
238
|
-
*
|
|
234
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
235
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
239
236
|
*/
|
|
240
237
|
entityFqdn?: string;
|
|
241
238
|
/**
|
|
242
|
-
*
|
|
243
|
-
*
|
|
244
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
239
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
240
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
245
241
|
*/
|
|
246
242
|
slug?: string;
|
|
247
243
|
/** ID of the entity associated with the event. */
|
|
248
244
|
entityId?: string;
|
|
249
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
245
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
250
246
|
eventTime?: Date | null;
|
|
251
247
|
/**
|
|
252
248
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -256,12 +252,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
256
252
|
/** If present, indicates the action that triggered the event. */
|
|
257
253
|
originatedFrom?: string | null;
|
|
258
254
|
/**
|
|
259
|
-
* A sequence number
|
|
260
|
-
*
|
|
261
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
262
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
263
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
264
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
255
|
+
* 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.
|
|
256
|
+
* 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.
|
|
265
257
|
*/
|
|
266
258
|
entityEventSequence?: string | null;
|
|
267
259
|
}
|
|
@@ -287,7 +279,7 @@ export interface EntityUpdatedEvent {
|
|
|
287
279
|
currentEntity?: string;
|
|
288
280
|
}
|
|
289
281
|
export interface EntityDeletedEvent {
|
|
290
|
-
/** Entity that was deleted */
|
|
282
|
+
/** Entity that was deleted. */
|
|
291
283
|
deletedEntity?: string | null;
|
|
292
284
|
}
|
|
293
285
|
export interface ActionEvent {
|
|
@@ -378,25 +370,21 @@ export interface BaseEventMetadata {
|
|
|
378
370
|
identity?: IdentificationData;
|
|
379
371
|
}
|
|
380
372
|
export interface EventMetadata extends BaseEventMetadata {
|
|
381
|
-
/**
|
|
382
|
-
* Unique event ID.
|
|
383
|
-
* Allows clients to ignore duplicate webhooks.
|
|
384
|
-
*/
|
|
373
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
385
374
|
_id?: string;
|
|
386
375
|
/**
|
|
387
|
-
*
|
|
388
|
-
*
|
|
376
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
377
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
389
378
|
*/
|
|
390
379
|
entityFqdn?: string;
|
|
391
380
|
/**
|
|
392
|
-
*
|
|
393
|
-
*
|
|
394
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
381
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
382
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
395
383
|
*/
|
|
396
384
|
slug?: string;
|
|
397
385
|
/** ID of the entity associated with the event. */
|
|
398
386
|
entityId?: string;
|
|
399
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
387
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
400
388
|
eventTime?: Date | null;
|
|
401
389
|
/**
|
|
402
390
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -406,12 +394,8 @@ export interface EventMetadata extends BaseEventMetadata {
|
|
|
406
394
|
/** If present, indicates the action that triggered the event. */
|
|
407
395
|
originatedFrom?: string | null;
|
|
408
396
|
/**
|
|
409
|
-
* A sequence number
|
|
410
|
-
*
|
|
411
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
412
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
413
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
414
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
397
|
+
* 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.
|
|
398
|
+
* 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.
|
|
415
399
|
*/
|
|
416
400
|
entityEventSequence?: string | null;
|
|
417
401
|
}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.universal.js","sourceRoot":"","sources":["../../../src/ecom-v1-checkout-settings-checkout-settings.universal.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,sEAAuF;AACvF,oFAGiD;AAEjD,2HAA6G;AAC7G,kEAAsF;AACtF,kEAAsF;AACtF,sFAAkF;AAsMlF,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,wBAAR,QAAQ,QAKnB;AAED,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,yBAAT,SAAS,QAIpB;
|
|
1
|
+
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.universal.js","sourceRoot":"","sources":["../../../src/ecom-v1-checkout-settings-checkout-settings.universal.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,sEAAuF;AACvF,oFAGiD;AAEjD,2HAA6G;AAC7G,kEAAsF;AACtF,kEAAsF;AACtF,sFAAkF;AAsMlF,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,wBAAR,QAAQ,QAKnB;AAED,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,yBAAT,SAAS,QAIpB;AA6KD,IAAY,mBAMX;AAND,WAAY,mBAAmB;IAC7B,0CAAmB,CAAA;IACnB,8DAAuC,CAAA;IACvC,wCAAiB,CAAA;IACjB,4CAAqB,CAAA;IACrB,kCAAW,CAAA;AACb,CAAC,EANW,mBAAmB,mCAAnB,mBAAmB,QAM9B;AAoFD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACI,KAAK,UAAU,mBAAmB;IAQvC,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,IAAA,8DAAqC,EAAC,EAAE,CAAC,CAAC;IAE1D,MAAM,OAAO,GACX,mCAAmC,CAAC,mBAAmB,CAAC,OAAO,CAAC,CAAC;IAEnE,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACjD,WAAW,EAAE,SAAS,EAAE,CAAC,MAAM,CAAC,CAAC;QAEjC,OAAO,IAAA,gEAAuC,EAC5C,IAAA,gCAAc,EAAC,MAAM,CAAC,IAAI,EAAE;YAC1B;gBACE,WAAW,EAAE,oCAA4B;gBACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;aACtE;SACF,CAAC,CACF,CAAC;IACL,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,IAAA,gCAAiB,EACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE;YAC5B,uBAAuB,EAAE,KAAK;SAC/B,EACD,EAAE,CACH,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC;AA9CD,kDA8CC;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACI,KAAK,UAAU,sBAAsB,CAC1C,gBAAkC;IASlC,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,IAAA,gCAAc,EAC5B,IAAA,8DAAqC,EAAC;QACpC,gBAAgB,EAAE,gBAAgB;KACnC,CAAC,EACF;QACE;YACE,WAAW,EAAE,oCAA4B;YACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;SACtE;KACF,CACF,CAAC;IAEF,MAAM,OAAO,GACX,mCAAmC,CAAC,sBAAsB,CAAC,OAAO,CAAC,CAAC;IAEtE,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACjD,WAAW,EAAE,SAAS,EAAE,CAAC,MAAM,CAAC,CAAC;QAEjC,OAAO,IAAA,gEAAuC,EAC5C,IAAA,gCAAc,EAAC,MAAM,CAAC,IAAI,EAAE;YAC1B;gBACE,WAAW,EAAE,oCAA4B;gBACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;aACtE;SACF,CAAC,CACF,CAAC;IACL,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,IAAA,gCAAiB,EACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE,gBAAgB,EAAE,MAAM,EAAE;YACtD,uBAAuB,EAAE,KAAK;SAC/B,EACD,CAAC,kBAAkB,CAAC,CACrB,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC;AA1DD,wDA0DC"}
|
|
@@ -250,25 +250,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
250
250
|
updatedEvent?: EntityUpdatedEvent;
|
|
251
251
|
deletedEvent?: EntityDeletedEvent;
|
|
252
252
|
actionEvent?: ActionEvent;
|
|
253
|
-
/**
|
|
254
|
-
* Unique event ID.
|
|
255
|
-
* Allows clients to ignore duplicate webhooks.
|
|
256
|
-
*/
|
|
253
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
257
254
|
id?: string;
|
|
258
255
|
/**
|
|
259
|
-
*
|
|
260
|
-
*
|
|
256
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
257
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
261
258
|
*/
|
|
262
259
|
entityFqdn?: string;
|
|
263
260
|
/**
|
|
264
|
-
*
|
|
265
|
-
*
|
|
266
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
261
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
262
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
267
263
|
*/
|
|
268
264
|
slug?: string;
|
|
269
265
|
/** ID of the entity associated with the event. */
|
|
270
266
|
entityId?: string;
|
|
271
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
267
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
272
268
|
eventTime?: Date | null;
|
|
273
269
|
/**
|
|
274
270
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -278,12 +274,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
278
274
|
/** If present, indicates the action that triggered the event. */
|
|
279
275
|
originatedFrom?: string | null;
|
|
280
276
|
/**
|
|
281
|
-
* A sequence number
|
|
282
|
-
*
|
|
283
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
284
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
285
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
286
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
277
|
+
* 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.
|
|
278
|
+
* 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.
|
|
287
279
|
*/
|
|
288
280
|
entityEventSequence?: string | null;
|
|
289
281
|
}
|
|
@@ -311,7 +303,7 @@ export interface EntityUpdatedEvent {
|
|
|
311
303
|
currentEntityAsJson?: string;
|
|
312
304
|
}
|
|
313
305
|
export interface EntityDeletedEvent {
|
|
314
|
-
/** Entity that was deleted */
|
|
306
|
+
/** Entity that was deleted. */
|
|
315
307
|
deletedEntityAsJson?: string | null;
|
|
316
308
|
}
|
|
317
309
|
export interface ActionEvent {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.types.js","sourceRoot":"","sources":["../../../src/ecom-v1-checkout-settings-checkout-settings.types.ts"],"names":[],"mappings":"AA4NA,MAAM,CAAN,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,KAAR,QAAQ,QAKnB;AAED,MAAM,CAAN,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,KAAT,SAAS,QAIpB;
|
|
1
|
+
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.types.js","sourceRoot":"","sources":["../../../src/ecom-v1-checkout-settings-checkout-settings.types.ts"],"names":[],"mappings":"AA4NA,MAAM,CAAN,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,KAAR,QAAQ,QAKnB;AAED,MAAM,CAAN,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,KAAT,SAAS,QAIpB;AA+KD,MAAM,CAAN,IAAY,mBAMX;AAND,WAAY,mBAAmB;IAC7B,0CAAmB,CAAA;IACnB,8DAAuC,CAAA;IACvC,wCAAiB,CAAA;IACjB,4CAAqB,CAAA;IACrB,kCAAW,CAAA;AACb,CAAC,EANW,mBAAmB,KAAnB,mBAAmB,QAM9B"}
|
|
@@ -228,25 +228,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
228
228
|
updatedEvent?: EntityUpdatedEvent;
|
|
229
229
|
deletedEvent?: EntityDeletedEvent;
|
|
230
230
|
actionEvent?: ActionEvent;
|
|
231
|
-
/**
|
|
232
|
-
* Unique event ID.
|
|
233
|
-
* Allows clients to ignore duplicate webhooks.
|
|
234
|
-
*/
|
|
231
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
235
232
|
_id?: string;
|
|
236
233
|
/**
|
|
237
|
-
*
|
|
238
|
-
*
|
|
234
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
235
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
239
236
|
*/
|
|
240
237
|
entityFqdn?: string;
|
|
241
238
|
/**
|
|
242
|
-
*
|
|
243
|
-
*
|
|
244
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
239
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
240
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
245
241
|
*/
|
|
246
242
|
slug?: string;
|
|
247
243
|
/** ID of the entity associated with the event. */
|
|
248
244
|
entityId?: string;
|
|
249
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
245
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
250
246
|
eventTime?: Date | null;
|
|
251
247
|
/**
|
|
252
248
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -256,12 +252,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
256
252
|
/** If present, indicates the action that triggered the event. */
|
|
257
253
|
originatedFrom?: string | null;
|
|
258
254
|
/**
|
|
259
|
-
* A sequence number
|
|
260
|
-
*
|
|
261
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
262
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
263
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
264
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
255
|
+
* 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.
|
|
256
|
+
* 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.
|
|
265
257
|
*/
|
|
266
258
|
entityEventSequence?: string | null;
|
|
267
259
|
}
|
|
@@ -287,7 +279,7 @@ export interface EntityUpdatedEvent {
|
|
|
287
279
|
currentEntity?: string;
|
|
288
280
|
}
|
|
289
281
|
export interface EntityDeletedEvent {
|
|
290
|
-
/** Entity that was deleted */
|
|
282
|
+
/** Entity that was deleted. */
|
|
291
283
|
deletedEntity?: string | null;
|
|
292
284
|
}
|
|
293
285
|
export interface ActionEvent {
|
|
@@ -378,25 +370,21 @@ export interface BaseEventMetadata {
|
|
|
378
370
|
identity?: IdentificationData;
|
|
379
371
|
}
|
|
380
372
|
export interface EventMetadata extends BaseEventMetadata {
|
|
381
|
-
/**
|
|
382
|
-
* Unique event ID.
|
|
383
|
-
* Allows clients to ignore duplicate webhooks.
|
|
384
|
-
*/
|
|
373
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
385
374
|
_id?: string;
|
|
386
375
|
/**
|
|
387
|
-
*
|
|
388
|
-
*
|
|
376
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
377
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
389
378
|
*/
|
|
390
379
|
entityFqdn?: string;
|
|
391
380
|
/**
|
|
392
|
-
*
|
|
393
|
-
*
|
|
394
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
381
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
382
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
395
383
|
*/
|
|
396
384
|
slug?: string;
|
|
397
385
|
/** ID of the entity associated with the event. */
|
|
398
386
|
entityId?: string;
|
|
399
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
387
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
400
388
|
eventTime?: Date | null;
|
|
401
389
|
/**
|
|
402
390
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -406,12 +394,8 @@ export interface EventMetadata extends BaseEventMetadata {
|
|
|
406
394
|
/** If present, indicates the action that triggered the event. */
|
|
407
395
|
originatedFrom?: string | null;
|
|
408
396
|
/**
|
|
409
|
-
* A sequence number
|
|
410
|
-
*
|
|
411
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
412
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
413
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
414
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
397
|
+
* 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.
|
|
398
|
+
* 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.
|
|
415
399
|
*/
|
|
416
400
|
entityEventSequence?: string | null;
|
|
417
401
|
}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.universal.js","sourceRoot":"","sources":["../../../src/ecom-v1-checkout-settings-checkout-settings.universal.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,IAAI,iBAAiB,EAAE,MAAM,kCAAkC,CAAC;AACvF,OAAO,EACL,qCAAqC,EACrC,uCAAuC,GACxC,MAAM,yCAAyC,CAAC;AAEjD,OAAO,KAAK,mCAAmC,MAAM,uDAAuD,CAAC;AAC7G,OAAO,EAAE,4BAA4B,EAAE,MAAM,wCAAwC,CAAC;AACtF,OAAO,EAAE,4BAA4B,EAAE,MAAM,wCAAwC,CAAC;AACtF,OAAO,EAAE,cAAc,EAAE,MAAM,kDAAkD,CAAC;AAsMlF,MAAM,CAAN,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,KAAR,QAAQ,QAKnB;AAED,MAAM,CAAN,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,KAAT,SAAS,QAIpB;
|
|
1
|
+
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.universal.js","sourceRoot":"","sources":["../../../src/ecom-v1-checkout-settings-checkout-settings.universal.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,IAAI,iBAAiB,EAAE,MAAM,kCAAkC,CAAC;AACvF,OAAO,EACL,qCAAqC,EACrC,uCAAuC,GACxC,MAAM,yCAAyC,CAAC;AAEjD,OAAO,KAAK,mCAAmC,MAAM,uDAAuD,CAAC;AAC7G,OAAO,EAAE,4BAA4B,EAAE,MAAM,wCAAwC,CAAC;AACtF,OAAO,EAAE,4BAA4B,EAAE,MAAM,wCAAwC,CAAC;AACtF,OAAO,EAAE,cAAc,EAAE,MAAM,kDAAkD,CAAC;AAsMlF,MAAM,CAAN,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,KAAR,QAAQ,QAKnB;AAED,MAAM,CAAN,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,KAAT,SAAS,QAIpB;AA6KD,MAAM,CAAN,IAAY,mBAMX;AAND,WAAY,mBAAmB;IAC7B,0CAAmB,CAAA;IACnB,8DAAuC,CAAA;IACvC,wCAAiB,CAAA;IACjB,4CAAqB,CAAA;IACrB,kCAAW,CAAA;AACb,CAAC,EANW,mBAAmB,KAAnB,mBAAmB,QAM9B;AAoFD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,CAAC,KAAK,UAAU,mBAAmB;IAQvC,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,qCAAqC,CAAC,EAAE,CAAC,CAAC;IAE1D,MAAM,OAAO,GACX,mCAAmC,CAAC,mBAAmB,CAAC,OAAO,CAAC,CAAC;IAEnE,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACjD,WAAW,EAAE,SAAS,EAAE,CAAC,MAAM,CAAC,CAAC;QAEjC,OAAO,uCAAuC,CAC5C,cAAc,CAAC,MAAM,CAAC,IAAI,EAAE;YAC1B;gBACE,WAAW,EAAE,4BAA4B;gBACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;aACtE;SACF,CAAC,CACF,CAAC;IACL,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,iBAAiB,CACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE;YAC5B,uBAAuB,EAAE,KAAK;SAC/B,EACD,EAAE,CACH,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,CAAC,KAAK,UAAU,sBAAsB,CAC1C,gBAAkC;IASlC,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,cAAc,CAC5B,qCAAqC,CAAC;QACpC,gBAAgB,EAAE,gBAAgB;KACnC,CAAC,EACF;QACE;YACE,WAAW,EAAE,4BAA4B;YACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;SACtE;KACF,CACF,CAAC;IAEF,MAAM,OAAO,GACX,mCAAmC,CAAC,sBAAsB,CAAC,OAAO,CAAC,CAAC;IAEtE,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACjD,WAAW,EAAE,SAAS,EAAE,CAAC,MAAM,CAAC,CAAC;QAEjC,OAAO,uCAAuC,CAC5C,cAAc,CAAC,MAAM,CAAC,IAAI,EAAE;YAC1B;gBACE,WAAW,EAAE,4BAA4B;gBACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;aACtE;SACF,CAAC,CACF,CAAC;IACL,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,iBAAiB,CACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE,gBAAgB,EAAE,MAAM,EAAE;YACtD,uBAAuB,EAAE,KAAK;SAC/B,EACD,CAAC,kBAAkB,CAAC,CACrB,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC"}
|
|
@@ -250,25 +250,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
250
250
|
updatedEvent?: EntityUpdatedEvent;
|
|
251
251
|
deletedEvent?: EntityDeletedEvent;
|
|
252
252
|
actionEvent?: ActionEvent;
|
|
253
|
-
/**
|
|
254
|
-
* Unique event ID.
|
|
255
|
-
* Allows clients to ignore duplicate webhooks.
|
|
256
|
-
*/
|
|
253
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
257
254
|
id?: string;
|
|
258
255
|
/**
|
|
259
|
-
*
|
|
260
|
-
*
|
|
256
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
257
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
261
258
|
*/
|
|
262
259
|
entityFqdn?: string;
|
|
263
260
|
/**
|
|
264
|
-
*
|
|
265
|
-
*
|
|
266
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
261
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
262
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
267
263
|
*/
|
|
268
264
|
slug?: string;
|
|
269
265
|
/** ID of the entity associated with the event. */
|
|
270
266
|
entityId?: string;
|
|
271
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
267
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
272
268
|
eventTime?: Date | null;
|
|
273
269
|
/**
|
|
274
270
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -278,12 +274,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
278
274
|
/** If present, indicates the action that triggered the event. */
|
|
279
275
|
originatedFrom?: string | null;
|
|
280
276
|
/**
|
|
281
|
-
* A sequence number
|
|
282
|
-
*
|
|
283
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
284
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
285
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
286
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
277
|
+
* 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.
|
|
278
|
+
* 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.
|
|
287
279
|
*/
|
|
288
280
|
entityEventSequence?: string | null;
|
|
289
281
|
}
|
|
@@ -311,7 +303,7 @@ export interface EntityUpdatedEvent {
|
|
|
311
303
|
currentEntityAsJson?: string;
|
|
312
304
|
}
|
|
313
305
|
export interface EntityDeletedEvent {
|
|
314
|
-
/** Entity that was deleted */
|
|
306
|
+
/** Entity that was deleted. */
|
|
315
307
|
deletedEntityAsJson?: string | null;
|
|
316
308
|
}
|
|
317
309
|
export interface ActionEvent {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.types.js","sourceRoot":"","sources":["../../../../src/ecom-v1-checkout-settings-checkout-settings.types.ts"],"names":[],"mappings":";;;AA4NA,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,wBAAR,QAAQ,QAKnB;AAED,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,yBAAT,SAAS,QAIpB;
|
|
1
|
+
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.types.js","sourceRoot":"","sources":["../../../../src/ecom-v1-checkout-settings-checkout-settings.types.ts"],"names":[],"mappings":";;;AA4NA,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,wBAAR,QAAQ,QAKnB;AAED,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,yBAAT,SAAS,QAIpB;AA+KD,IAAY,mBAMX;AAND,WAAY,mBAAmB;IAC7B,0CAAmB,CAAA;IACnB,8DAAuC,CAAA;IACvC,wCAAiB,CAAA;IACjB,4CAAqB,CAAA;IACrB,kCAAW,CAAA;AACb,CAAC,EANW,mBAAmB,mCAAnB,mBAAmB,QAM9B"}
|
|
@@ -228,25 +228,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
228
228
|
updatedEvent?: EntityUpdatedEvent;
|
|
229
229
|
deletedEvent?: EntityDeletedEvent;
|
|
230
230
|
actionEvent?: ActionEvent;
|
|
231
|
-
/**
|
|
232
|
-
* Unique event ID.
|
|
233
|
-
* Allows clients to ignore duplicate webhooks.
|
|
234
|
-
*/
|
|
231
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
235
232
|
_id?: string;
|
|
236
233
|
/**
|
|
237
|
-
*
|
|
238
|
-
*
|
|
234
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
235
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
239
236
|
*/
|
|
240
237
|
entityFqdn?: string;
|
|
241
238
|
/**
|
|
242
|
-
*
|
|
243
|
-
*
|
|
244
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
239
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
240
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
245
241
|
*/
|
|
246
242
|
slug?: string;
|
|
247
243
|
/** ID of the entity associated with the event. */
|
|
248
244
|
entityId?: string;
|
|
249
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
245
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
250
246
|
eventTime?: Date | null;
|
|
251
247
|
/**
|
|
252
248
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -256,12 +252,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
256
252
|
/** If present, indicates the action that triggered the event. */
|
|
257
253
|
originatedFrom?: string | null;
|
|
258
254
|
/**
|
|
259
|
-
* A sequence number
|
|
260
|
-
*
|
|
261
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
262
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
263
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
264
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
255
|
+
* 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.
|
|
256
|
+
* 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.
|
|
265
257
|
*/
|
|
266
258
|
entityEventSequence?: string | null;
|
|
267
259
|
}
|
|
@@ -287,7 +279,7 @@ export interface EntityUpdatedEvent {
|
|
|
287
279
|
currentEntity?: string;
|
|
288
280
|
}
|
|
289
281
|
export interface EntityDeletedEvent {
|
|
290
|
-
/** Entity that was deleted */
|
|
282
|
+
/** Entity that was deleted. */
|
|
291
283
|
deletedEntity?: string | null;
|
|
292
284
|
}
|
|
293
285
|
export interface ActionEvent {
|
|
@@ -378,25 +370,21 @@ export interface BaseEventMetadata {
|
|
|
378
370
|
identity?: IdentificationData;
|
|
379
371
|
}
|
|
380
372
|
export interface EventMetadata extends BaseEventMetadata {
|
|
381
|
-
/**
|
|
382
|
-
* Unique event ID.
|
|
383
|
-
* Allows clients to ignore duplicate webhooks.
|
|
384
|
-
*/
|
|
373
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
385
374
|
_id?: string;
|
|
386
375
|
/**
|
|
387
|
-
*
|
|
388
|
-
*
|
|
376
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
377
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
389
378
|
*/
|
|
390
379
|
entityFqdn?: string;
|
|
391
380
|
/**
|
|
392
|
-
*
|
|
393
|
-
*
|
|
394
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
381
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
382
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
395
383
|
*/
|
|
396
384
|
slug?: string;
|
|
397
385
|
/** ID of the entity associated with the event. */
|
|
398
386
|
entityId?: string;
|
|
399
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
387
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
400
388
|
eventTime?: Date | null;
|
|
401
389
|
/**
|
|
402
390
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -406,12 +394,8 @@ export interface EventMetadata extends BaseEventMetadata {
|
|
|
406
394
|
/** If present, indicates the action that triggered the event. */
|
|
407
395
|
originatedFrom?: string | null;
|
|
408
396
|
/**
|
|
409
|
-
* A sequence number
|
|
410
|
-
*
|
|
411
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
412
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
413
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
414
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
397
|
+
* 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.
|
|
398
|
+
* 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.
|
|
415
399
|
*/
|
|
416
400
|
entityEventSequence?: string | null;
|
|
417
401
|
}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.universal.js","sourceRoot":"","sources":["../../../../src/ecom-v1-checkout-settings-checkout-settings.universal.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,sEAAuF;AACvF,oFAGiD;AAEjD,2HAA6G;AAC7G,kEAAsF;AACtF,kEAAsF;AACtF,sFAAkF;AAsMlF,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,wBAAR,QAAQ,QAKnB;AAED,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,yBAAT,SAAS,QAIpB;
|
|
1
|
+
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.universal.js","sourceRoot":"","sources":["../../../../src/ecom-v1-checkout-settings-checkout-settings.universal.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,sEAAuF;AACvF,oFAGiD;AAEjD,2HAA6G;AAC7G,kEAAsF;AACtF,kEAAsF;AACtF,sFAAkF;AAsMlF,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,wBAAR,QAAQ,QAKnB;AAED,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,yBAAT,SAAS,QAIpB;AA6KD,IAAY,mBAMX;AAND,WAAY,mBAAmB;IAC7B,0CAAmB,CAAA;IACnB,8DAAuC,CAAA;IACvC,wCAAiB,CAAA;IACjB,4CAAqB,CAAA;IACrB,kCAAW,CAAA;AACb,CAAC,EANW,mBAAmB,mCAAnB,mBAAmB,QAM9B;AAoFD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACI,KAAK,UAAU,mBAAmB;IAQvC,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,IAAA,8DAAqC,EAAC,EAAE,CAAC,CAAC;IAE1D,MAAM,OAAO,GACX,mCAAmC,CAAC,mBAAmB,CAAC,OAAO,CAAC,CAAC;IAEnE,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACjD,WAAW,EAAE,SAAS,EAAE,CAAC,MAAM,CAAC,CAAC;QAEjC,OAAO,IAAA,gEAAuC,EAC5C,IAAA,gCAAc,EAAC,MAAM,CAAC,IAAI,EAAE;YAC1B;gBACE,WAAW,EAAE,oCAA4B;gBACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;aACtE;SACF,CAAC,CACF,CAAC;IACL,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,IAAA,gCAAiB,EACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE;YAC5B,uBAAuB,EAAE,KAAK;SAC/B,EACD,EAAE,CACH,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC;AA9CD,kDA8CC;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACI,KAAK,UAAU,sBAAsB,CAC1C,gBAAkC;IASlC,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,IAAA,gCAAc,EAC5B,IAAA,8DAAqC,EAAC;QACpC,gBAAgB,EAAE,gBAAgB;KACnC,CAAC,EACF;QACE;YACE,WAAW,EAAE,oCAA4B;YACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;SACtE;KACF,CACF,CAAC;IAEF,MAAM,OAAO,GACX,mCAAmC,CAAC,sBAAsB,CAAC,OAAO,CAAC,CAAC;IAEtE,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACjD,WAAW,EAAE,SAAS,EAAE,CAAC,MAAM,CAAC,CAAC;QAEjC,OAAO,IAAA,gEAAuC,EAC5C,IAAA,gCAAc,EAAC,MAAM,CAAC,IAAI,EAAE;YAC1B;gBACE,WAAW,EAAE,oCAA4B;gBACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;aACtE;SACF,CAAC,CACF,CAAC;IACL,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,IAAA,gCAAiB,EACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE,gBAAgB,EAAE,MAAM,EAAE;YACtD,uBAAuB,EAAE,KAAK;SAC/B,EACD,CAAC,kBAAkB,CAAC,CACrB,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC;AA1DD,wDA0DC"}
|
|
@@ -250,25 +250,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
250
250
|
updatedEvent?: EntityUpdatedEvent;
|
|
251
251
|
deletedEvent?: EntityDeletedEvent;
|
|
252
252
|
actionEvent?: ActionEvent;
|
|
253
|
-
/**
|
|
254
|
-
* Unique event ID.
|
|
255
|
-
* Allows clients to ignore duplicate webhooks.
|
|
256
|
-
*/
|
|
253
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
257
254
|
id?: string;
|
|
258
255
|
/**
|
|
259
|
-
*
|
|
260
|
-
*
|
|
256
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
257
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
261
258
|
*/
|
|
262
259
|
entityFqdn?: string;
|
|
263
260
|
/**
|
|
264
|
-
*
|
|
265
|
-
*
|
|
266
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
261
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
262
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
267
263
|
*/
|
|
268
264
|
slug?: string;
|
|
269
265
|
/** ID of the entity associated with the event. */
|
|
270
266
|
entityId?: string;
|
|
271
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
267
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
272
268
|
eventTime?: Date | null;
|
|
273
269
|
/**
|
|
274
270
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -278,12 +274,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
278
274
|
/** If present, indicates the action that triggered the event. */
|
|
279
275
|
originatedFrom?: string | null;
|
|
280
276
|
/**
|
|
281
|
-
* A sequence number
|
|
282
|
-
*
|
|
283
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
284
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
285
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
286
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
277
|
+
* 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.
|
|
278
|
+
* 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.
|
|
287
279
|
*/
|
|
288
280
|
entityEventSequence?: string | null;
|
|
289
281
|
}
|
|
@@ -311,7 +303,7 @@ export interface EntityUpdatedEvent {
|
|
|
311
303
|
currentEntityAsJson?: string;
|
|
312
304
|
}
|
|
313
305
|
export interface EntityDeletedEvent {
|
|
314
|
-
/** Entity that was deleted */
|
|
306
|
+
/** Entity that was deleted. */
|
|
315
307
|
deletedEntityAsJson?: string | null;
|
|
316
308
|
}
|
|
317
309
|
export interface ActionEvent {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.types.js","sourceRoot":"","sources":["../../../../src/ecom-v1-checkout-settings-checkout-settings.types.ts"],"names":[],"mappings":"AA4NA,MAAM,CAAN,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,KAAR,QAAQ,QAKnB;AAED,MAAM,CAAN,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,KAAT,SAAS,QAIpB;
|
|
1
|
+
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.types.js","sourceRoot":"","sources":["../../../../src/ecom-v1-checkout-settings-checkout-settings.types.ts"],"names":[],"mappings":"AA4NA,MAAM,CAAN,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,KAAR,QAAQ,QAKnB;AAED,MAAM,CAAN,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,KAAT,SAAS,QAIpB;AA+KD,MAAM,CAAN,IAAY,mBAMX;AAND,WAAY,mBAAmB;IAC7B,0CAAmB,CAAA;IACnB,8DAAuC,CAAA;IACvC,wCAAiB,CAAA;IACjB,4CAAqB,CAAA;IACrB,kCAAW,CAAA;AACb,CAAC,EANW,mBAAmB,KAAnB,mBAAmB,QAM9B"}
|
|
@@ -228,25 +228,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
228
228
|
updatedEvent?: EntityUpdatedEvent;
|
|
229
229
|
deletedEvent?: EntityDeletedEvent;
|
|
230
230
|
actionEvent?: ActionEvent;
|
|
231
|
-
/**
|
|
232
|
-
* Unique event ID.
|
|
233
|
-
* Allows clients to ignore duplicate webhooks.
|
|
234
|
-
*/
|
|
231
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
235
232
|
_id?: string;
|
|
236
233
|
/**
|
|
237
|
-
*
|
|
238
|
-
*
|
|
234
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
235
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
239
236
|
*/
|
|
240
237
|
entityFqdn?: string;
|
|
241
238
|
/**
|
|
242
|
-
*
|
|
243
|
-
*
|
|
244
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
239
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
240
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
245
241
|
*/
|
|
246
242
|
slug?: string;
|
|
247
243
|
/** ID of the entity associated with the event. */
|
|
248
244
|
entityId?: string;
|
|
249
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
245
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
250
246
|
eventTime?: Date | null;
|
|
251
247
|
/**
|
|
252
248
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -256,12 +252,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
256
252
|
/** If present, indicates the action that triggered the event. */
|
|
257
253
|
originatedFrom?: string | null;
|
|
258
254
|
/**
|
|
259
|
-
* A sequence number
|
|
260
|
-
*
|
|
261
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
262
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
263
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
264
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
255
|
+
* 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.
|
|
256
|
+
* 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.
|
|
265
257
|
*/
|
|
266
258
|
entityEventSequence?: string | null;
|
|
267
259
|
}
|
|
@@ -287,7 +279,7 @@ export interface EntityUpdatedEvent {
|
|
|
287
279
|
currentEntity?: string;
|
|
288
280
|
}
|
|
289
281
|
export interface EntityDeletedEvent {
|
|
290
|
-
/** Entity that was deleted */
|
|
282
|
+
/** Entity that was deleted. */
|
|
291
283
|
deletedEntity?: string | null;
|
|
292
284
|
}
|
|
293
285
|
export interface ActionEvent {
|
|
@@ -378,25 +370,21 @@ export interface BaseEventMetadata {
|
|
|
378
370
|
identity?: IdentificationData;
|
|
379
371
|
}
|
|
380
372
|
export interface EventMetadata extends BaseEventMetadata {
|
|
381
|
-
/**
|
|
382
|
-
* Unique event ID.
|
|
383
|
-
* Allows clients to ignore duplicate webhooks.
|
|
384
|
-
*/
|
|
373
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
385
374
|
_id?: string;
|
|
386
375
|
/**
|
|
387
|
-
*
|
|
388
|
-
*
|
|
376
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
377
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
389
378
|
*/
|
|
390
379
|
entityFqdn?: string;
|
|
391
380
|
/**
|
|
392
|
-
*
|
|
393
|
-
*
|
|
394
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
381
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
382
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
395
383
|
*/
|
|
396
384
|
slug?: string;
|
|
397
385
|
/** ID of the entity associated with the event. */
|
|
398
386
|
entityId?: string;
|
|
399
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
387
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
400
388
|
eventTime?: Date | null;
|
|
401
389
|
/**
|
|
402
390
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -406,12 +394,8 @@ export interface EventMetadata extends BaseEventMetadata {
|
|
|
406
394
|
/** If present, indicates the action that triggered the event. */
|
|
407
395
|
originatedFrom?: string | null;
|
|
408
396
|
/**
|
|
409
|
-
* A sequence number
|
|
410
|
-
*
|
|
411
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
412
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
413
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
414
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
397
|
+
* 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.
|
|
398
|
+
* 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.
|
|
415
399
|
*/
|
|
416
400
|
entityEventSequence?: string | null;
|
|
417
401
|
}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.universal.js","sourceRoot":"","sources":["../../../../src/ecom-v1-checkout-settings-checkout-settings.universal.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,IAAI,iBAAiB,EAAE,MAAM,kCAAkC,CAAC;AACvF,OAAO,EACL,qCAAqC,EACrC,uCAAuC,GACxC,MAAM,yCAAyC,CAAC;AAEjD,OAAO,KAAK,mCAAmC,MAAM,uDAAuD,CAAC;AAC7G,OAAO,EAAE,4BAA4B,EAAE,MAAM,wCAAwC,CAAC;AACtF,OAAO,EAAE,4BAA4B,EAAE,MAAM,wCAAwC,CAAC;AACtF,OAAO,EAAE,cAAc,EAAE,MAAM,kDAAkD,CAAC;AAsMlF,MAAM,CAAN,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,KAAR,QAAQ,QAKnB;AAED,MAAM,CAAN,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,KAAT,SAAS,QAIpB;
|
|
1
|
+
{"version":3,"file":"ecom-v1-checkout-settings-checkout-settings.universal.js","sourceRoot":"","sources":["../../../../src/ecom-v1-checkout-settings-checkout-settings.universal.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,IAAI,iBAAiB,EAAE,MAAM,kCAAkC,CAAC;AACvF,OAAO,EACL,qCAAqC,EACrC,uCAAuC,GACxC,MAAM,yCAAyC,CAAC;AAEjD,OAAO,KAAK,mCAAmC,MAAM,uDAAuD,CAAC;AAC7G,OAAO,EAAE,4BAA4B,EAAE,MAAM,wCAAwC,CAAC;AACtF,OAAO,EAAE,4BAA4B,EAAE,MAAM,wCAAwC,CAAC;AACtF,OAAO,EAAE,cAAc,EAAE,MAAM,kDAAkD,CAAC;AAsMlF,MAAM,CAAN,IAAY,QAKX;AALD,WAAY,QAAQ;IAClB,mDAAuC,CAAA;IACvC,2BAAe,CAAA;IACf,6BAAiB,CAAA;IACjB,2BAAe,CAAA;AACjB,CAAC,EALW,QAAQ,KAAR,QAAQ,QAKnB;AAED,MAAM,CAAN,IAAY,SAIX;AAJD,WAAY,SAAS;IACnB,oDAAuC,CAAA;IACvC,0BAAa,CAAA;IACb,8BAAiB,CAAA;AACnB,CAAC,EAJW,SAAS,KAAT,SAAS,QAIpB;AA6KD,MAAM,CAAN,IAAY,mBAMX;AAND,WAAY,mBAAmB;IAC7B,0CAAmB,CAAA;IACnB,8DAAuC,CAAA;IACvC,wCAAiB,CAAA;IACjB,4CAAqB,CAAA;IACrB,kCAAW,CAAA;AACb,CAAC,EANW,mBAAmB,KAAnB,mBAAmB,QAM9B;AAoFD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,CAAC,KAAK,UAAU,mBAAmB;IAQvC,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,qCAAqC,CAAC,EAAE,CAAC,CAAC;IAE1D,MAAM,OAAO,GACX,mCAAmC,CAAC,mBAAmB,CAAC,OAAO,CAAC,CAAC;IAEnE,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACjD,WAAW,EAAE,SAAS,EAAE,CAAC,MAAM,CAAC,CAAC;QAEjC,OAAO,uCAAuC,CAC5C,cAAc,CAAC,MAAM,CAAC,IAAI,EAAE;YAC1B;gBACE,WAAW,EAAE,4BAA4B;gBACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;aACtE;SACF,CAAC,CACF,CAAC;IACL,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,iBAAiB,CACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE;YAC5B,uBAAuB,EAAE,KAAK;SAC/B,EACD,EAAE,CACH,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,CAAC,KAAK,UAAU,sBAAsB,CAC1C,gBAAkC;IASlC,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,cAAc,CAC5B,qCAAqC,CAAC;QACpC,gBAAgB,EAAE,gBAAgB;KACnC,CAAC,EACF;QACE;YACE,WAAW,EAAE,4BAA4B;YACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;SACtE;KACF,CACF,CAAC;IAEF,MAAM,OAAO,GACX,mCAAmC,CAAC,sBAAsB,CAAC,OAAO,CAAC,CAAC;IAEtE,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACjD,WAAW,EAAE,SAAS,EAAE,CAAC,MAAM,CAAC,CAAC;QAEjC,OAAO,uCAAuC,CAC5C,cAAc,CAAC,MAAM,CAAC,IAAI,EAAE;YAC1B;gBACE,WAAW,EAAE,4BAA4B;gBACzC,KAAK,EAAE,CAAC,EAAE,IAAI,EAAE,kDAAkD,EAAE,CAAC;aACtE;SACF,CAAC,CACF,CAAC;IACL,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,iBAAiB,CACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE,gBAAgB,EAAE,MAAM,EAAE;YACtD,uBAAuB,EAAE,KAAK;SAC/B,EACD,CAAC,kBAAkB,CAAC,CACrB,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC"}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wix/auto_sdk_ecom_checkout-settings",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.14",
|
|
4
4
|
"publishConfig": {
|
|
5
5
|
"registry": "https://registry.npmjs.org/",
|
|
6
6
|
"access": "public"
|
|
@@ -29,7 +29,7 @@
|
|
|
29
29
|
],
|
|
30
30
|
"dependencies": {
|
|
31
31
|
"@wix/sdk-runtime": "^0.3.49",
|
|
32
|
-
"@wix/sdk-types": "^1.13.
|
|
32
|
+
"@wix/sdk-types": "^1.13.23"
|
|
33
33
|
},
|
|
34
34
|
"devDependencies": {
|
|
35
35
|
"typescript": "^5.3.2"
|
|
@@ -48,5 +48,5 @@
|
|
|
48
48
|
"fqdn": "wix.ecom.v1.checkout_settings"
|
|
49
49
|
}
|
|
50
50
|
},
|
|
51
|
-
"falconPackageHash": "
|
|
51
|
+
"falconPackageHash": "32046d08b2fbd7082a9dcd9fe15a3926a00fddfe0857a043e3fcbf6d"
|
|
52
52
|
}
|