@wix/auto_sdk_ecom_orders-settings 1.0.8 → 1.0.9
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-orders-settings-orders-settings.types.d.ts +9 -17
- package/build/cjs/src/ecom-v1-orders-settings-orders-settings.types.js.map +1 -1
- package/build/cjs/src/ecom-v1-orders-settings-orders-settings.universal.d.ts +23 -33
- package/build/cjs/src/ecom-v1-orders-settings-orders-settings.universal.js +4 -0
- package/build/cjs/src/ecom-v1-orders-settings-orders-settings.universal.js.map +1 -1
- package/build/es/src/ecom-v1-orders-settings-orders-settings.types.d.ts +9 -17
- package/build/es/src/ecom-v1-orders-settings-orders-settings.types.js.map +1 -1
- package/build/es/src/ecom-v1-orders-settings-orders-settings.universal.d.ts +23 -33
- package/build/es/src/ecom-v1-orders-settings-orders-settings.universal.js +4 -0
- package/build/es/src/ecom-v1-orders-settings-orders-settings.universal.js.map +1 -1
- package/build/internal/cjs/src/ecom-v1-orders-settings-orders-settings.types.d.ts +9 -17
- package/build/internal/cjs/src/ecom-v1-orders-settings-orders-settings.types.js.map +1 -1
- package/build/internal/cjs/src/ecom-v1-orders-settings-orders-settings.universal.d.ts +23 -33
- package/build/internal/cjs/src/ecom-v1-orders-settings-orders-settings.universal.js +4 -0
- package/build/internal/cjs/src/ecom-v1-orders-settings-orders-settings.universal.js.map +1 -1
- package/build/internal/es/src/ecom-v1-orders-settings-orders-settings.types.d.ts +9 -17
- package/build/internal/es/src/ecom-v1-orders-settings-orders-settings.types.js.map +1 -1
- package/build/internal/es/src/ecom-v1-orders-settings-orders-settings.universal.d.ts +23 -33
- package/build/internal/es/src/ecom-v1-orders-settings-orders-settings.universal.js +4 -0
- package/build/internal/es/src/ecom-v1-orders-settings-orders-settings.universal.js.map +1 -1
- package/package.json +2 -2
|
@@ -59,25 +59,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
59
59
|
updatedEvent?: EntityUpdatedEvent;
|
|
60
60
|
deletedEvent?: EntityDeletedEvent;
|
|
61
61
|
actionEvent?: ActionEvent;
|
|
62
|
-
/**
|
|
63
|
-
* Unique event ID.
|
|
64
|
-
* Allows clients to ignore duplicate webhooks.
|
|
65
|
-
*/
|
|
62
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
66
63
|
id?: string;
|
|
67
64
|
/**
|
|
68
|
-
*
|
|
69
|
-
*
|
|
65
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
66
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
70
67
|
*/
|
|
71
68
|
entityFqdn?: string;
|
|
72
69
|
/**
|
|
73
|
-
*
|
|
74
|
-
*
|
|
75
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
70
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
71
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
76
72
|
*/
|
|
77
73
|
slug?: string;
|
|
78
74
|
/** ID of the entity associated with the event. */
|
|
79
75
|
entityId?: string;
|
|
80
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
76
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
81
77
|
eventTime?: Date | null;
|
|
82
78
|
/**
|
|
83
79
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -87,12 +83,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
87
83
|
/** If present, indicates the action that triggered the event. */
|
|
88
84
|
originatedFrom?: string | null;
|
|
89
85
|
/**
|
|
90
|
-
* A sequence number
|
|
91
|
-
*
|
|
92
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
93
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
94
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
95
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
86
|
+
* 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.
|
|
87
|
+
* 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.
|
|
96
88
|
*/
|
|
97
89
|
entityEventSequence?: string | null;
|
|
98
90
|
}
|
|
@@ -120,7 +112,7 @@ export interface EntityUpdatedEvent {
|
|
|
120
112
|
currentEntityAsJson?: string;
|
|
121
113
|
}
|
|
122
114
|
export interface EntityDeletedEvent {
|
|
123
|
-
/** Entity that was deleted */
|
|
115
|
+
/** Entity that was deleted. */
|
|
124
116
|
deletedEntityAsJson?: string | null;
|
|
125
117
|
}
|
|
126
118
|
export interface ActionEvent {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.types.js","sourceRoot":"","sources":["../../../src/ecom-v1-orders-settings-orders-settings.types.ts"],"names":[],"mappings":";;;AA0BA,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,sCAAtB,sBAAsB,QAMjC;
|
|
1
|
+
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.types.js","sourceRoot":"","sources":["../../../src/ecom-v1-orders-settings-orders-settings.types.ts"],"names":[],"mappings":";;;AA0BA,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,sCAAtB,sBAAsB,QAMjC;AAuKD,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"}
|
|
@@ -61,25 +61,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
61
61
|
updatedEvent?: EntityUpdatedEvent;
|
|
62
62
|
deletedEvent?: EntityDeletedEvent;
|
|
63
63
|
actionEvent?: ActionEvent;
|
|
64
|
-
/**
|
|
65
|
-
* Unique event ID.
|
|
66
|
-
* Allows clients to ignore duplicate webhooks.
|
|
67
|
-
*/
|
|
64
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
68
65
|
_id?: string;
|
|
69
66
|
/**
|
|
70
|
-
*
|
|
71
|
-
*
|
|
67
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
68
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
72
69
|
*/
|
|
73
70
|
entityFqdn?: string;
|
|
74
71
|
/**
|
|
75
|
-
*
|
|
76
|
-
*
|
|
77
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
72
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
73
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
78
74
|
*/
|
|
79
75
|
slug?: string;
|
|
80
76
|
/** ID of the entity associated with the event. */
|
|
81
77
|
entityId?: string;
|
|
82
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
78
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
83
79
|
eventTime?: Date | null;
|
|
84
80
|
/**
|
|
85
81
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -89,12 +85,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
89
85
|
/** If present, indicates the action that triggered the event. */
|
|
90
86
|
originatedFrom?: string | null;
|
|
91
87
|
/**
|
|
92
|
-
* A sequence number
|
|
93
|
-
*
|
|
94
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
95
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
96
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
97
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
88
|
+
* 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.
|
|
89
|
+
* 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.
|
|
98
90
|
*/
|
|
99
91
|
entityEventSequence?: string | null;
|
|
100
92
|
}
|
|
@@ -120,7 +112,7 @@ export interface EntityUpdatedEvent {
|
|
|
120
112
|
currentEntity?: string;
|
|
121
113
|
}
|
|
122
114
|
export interface EntityDeletedEvent {
|
|
123
|
-
/** Entity that was deleted */
|
|
115
|
+
/** Entity that was deleted. */
|
|
124
116
|
deletedEntity?: string | null;
|
|
125
117
|
}
|
|
126
118
|
export interface ActionEvent {
|
|
@@ -211,25 +203,21 @@ export interface BaseEventMetadata {
|
|
|
211
203
|
identity?: IdentificationData;
|
|
212
204
|
}
|
|
213
205
|
export interface EventMetadata extends BaseEventMetadata {
|
|
214
|
-
/**
|
|
215
|
-
* Unique event ID.
|
|
216
|
-
* Allows clients to ignore duplicate webhooks.
|
|
217
|
-
*/
|
|
206
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
218
207
|
_id?: string;
|
|
219
208
|
/**
|
|
220
|
-
*
|
|
221
|
-
*
|
|
209
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
210
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
222
211
|
*/
|
|
223
212
|
entityFqdn?: string;
|
|
224
213
|
/**
|
|
225
|
-
*
|
|
226
|
-
*
|
|
227
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
214
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
215
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
228
216
|
*/
|
|
229
217
|
slug?: string;
|
|
230
218
|
/** ID of the entity associated with the event. */
|
|
231
219
|
entityId?: string;
|
|
232
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
220
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
233
221
|
eventTime?: Date | null;
|
|
234
222
|
/**
|
|
235
223
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -239,12 +227,8 @@ export interface EventMetadata extends BaseEventMetadata {
|
|
|
239
227
|
/** If present, indicates the action that triggered the event. */
|
|
240
228
|
originatedFrom?: string | null;
|
|
241
229
|
/**
|
|
242
|
-
* A sequence number
|
|
243
|
-
*
|
|
244
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
245
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
246
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
247
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
230
|
+
* 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.
|
|
231
|
+
* 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.
|
|
248
232
|
*/
|
|
249
233
|
entityEventSequence?: string | null;
|
|
250
234
|
}
|
|
@@ -256,6 +240,8 @@ export interface OrdersSettingsUpdatedEnvelope {
|
|
|
256
240
|
* Triggered when orders settings are updated.
|
|
257
241
|
* @permissionScope Manage Stores - all permissions
|
|
258
242
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
243
|
+
* @permissionScope Manage Stores
|
|
244
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
259
245
|
* @permissionScope Read eCommerce - all read permissions
|
|
260
246
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
261
247
|
* @permissionScope Read Orders
|
|
@@ -287,6 +273,8 @@ type OrdersSettingsNonNullablePaths = `inventoryUpdateTrigger`;
|
|
|
287
273
|
* @permissionId ECOM.READ_ORDERS_SETTINGS
|
|
288
274
|
* @permissionScope Manage Stores - all permissions
|
|
289
275
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
276
|
+
* @permissionScope Manage Stores
|
|
277
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
290
278
|
* @permissionScope Read eCommerce - all read permissions
|
|
291
279
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
292
280
|
* @permissionScope Read Orders
|
|
@@ -319,6 +307,8 @@ export declare function getOrdersSettings(): Promise<NonNullablePaths<GetOrdersS
|
|
|
319
307
|
* @permissionId ECOM.UPDATE_ORDERS_SETTINGS
|
|
320
308
|
* @permissionScope Manage Stores - all permissions
|
|
321
309
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
310
|
+
* @permissionScope Manage Stores
|
|
311
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
322
312
|
* @permissionScope Manage Restaurants - all permissions
|
|
323
313
|
* @permissionScopeId SCOPE.RESTAURANTS.MEGA-SCOPES
|
|
324
314
|
* @permissionScope Manage eCommerce - all permissions
|
|
@@ -53,6 +53,8 @@ var WebhookIdentityType;
|
|
|
53
53
|
* @permissionId ECOM.READ_ORDERS_SETTINGS
|
|
54
54
|
* @permissionScope Manage Stores - all permissions
|
|
55
55
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
56
|
+
* @permissionScope Manage Stores
|
|
57
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
56
58
|
* @permissionScope Read eCommerce - all read permissions
|
|
57
59
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
58
60
|
* @permissionScope Read Orders
|
|
@@ -104,6 +106,8 @@ exports.getOrdersSettings = getOrdersSettings;
|
|
|
104
106
|
* @permissionId ECOM.UPDATE_ORDERS_SETTINGS
|
|
105
107
|
* @permissionScope Manage Stores - all permissions
|
|
106
108
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
109
|
+
* @permissionScope Manage Stores
|
|
110
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
107
111
|
* @permissionScope Manage Restaurants - all permissions
|
|
108
112
|
* @permissionScopeId SCOPE.RESTAURANTS.MEGA-SCOPES
|
|
109
113
|
* @permissionScope Manage eCommerce - all permissions
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.universal.js","sourceRoot":"","sources":["../../../src/ecom-v1-orders-settings-orders-settings.universal.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,sEAAuF;AACvF,oFAGiD;AAEjD,qHAAuG;AA6BvG,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,sCAAtB,sBAAsB,QAMjC;
|
|
1
|
+
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.universal.js","sourceRoot":"","sources":["../../../src/ecom-v1-orders-settings-orders-settings.universal.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,sEAAuF;AACvF,oFAGiD;AAEjD,qHAAuG;AA6BvG,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,sCAAtB,sBAAsB,QAMjC;AAqKD,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;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACI,KAAK,UAAU,iBAAiB;IAQrC,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,GAAG,iCAAiC,CAAC,iBAAiB,CAAC,OAAO,CAAC,CAAC;IAE7E,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,EAAC,MAAM,CAAC,IAAI,CAAE,CAAC;IAC/D,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;AAtCD,8CAsCC;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACI,KAAK,UAAU,oBAAoB,CACxC,cAA8B;IAS9B,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,IAAA,8DAAqC,EAAC;QACpD,cAAc,EAAE,cAAc;KAC/B,CAAC,CAAC;IAEH,MAAM,OAAO,GACX,iCAAiC,CAAC,oBAAoB,CAAC,OAAO,CAAC,CAAC;IAElE,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,EAAC,MAAM,CAAC,IAAI,CAAE,CAAC;IAC/D,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,IAAA,gCAAiB,EACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE,cAAc,EAAE,MAAM,EAAE;YACpD,uBAAuB,EAAE,KAAK;SAC/B,EACD,CAAC,gBAAgB,CAAC,CACnB,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC;AA3CD,oDA2CC"}
|
|
@@ -59,25 +59,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
59
59
|
updatedEvent?: EntityUpdatedEvent;
|
|
60
60
|
deletedEvent?: EntityDeletedEvent;
|
|
61
61
|
actionEvent?: ActionEvent;
|
|
62
|
-
/**
|
|
63
|
-
* Unique event ID.
|
|
64
|
-
* Allows clients to ignore duplicate webhooks.
|
|
65
|
-
*/
|
|
62
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
66
63
|
id?: string;
|
|
67
64
|
/**
|
|
68
|
-
*
|
|
69
|
-
*
|
|
65
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
66
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
70
67
|
*/
|
|
71
68
|
entityFqdn?: string;
|
|
72
69
|
/**
|
|
73
|
-
*
|
|
74
|
-
*
|
|
75
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
70
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
71
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
76
72
|
*/
|
|
77
73
|
slug?: string;
|
|
78
74
|
/** ID of the entity associated with the event. */
|
|
79
75
|
entityId?: string;
|
|
80
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
76
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
81
77
|
eventTime?: Date | null;
|
|
82
78
|
/**
|
|
83
79
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -87,12 +83,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
87
83
|
/** If present, indicates the action that triggered the event. */
|
|
88
84
|
originatedFrom?: string | null;
|
|
89
85
|
/**
|
|
90
|
-
* A sequence number
|
|
91
|
-
*
|
|
92
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
93
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
94
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
95
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
86
|
+
* 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.
|
|
87
|
+
* 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.
|
|
96
88
|
*/
|
|
97
89
|
entityEventSequence?: string | null;
|
|
98
90
|
}
|
|
@@ -120,7 +112,7 @@ export interface EntityUpdatedEvent {
|
|
|
120
112
|
currentEntityAsJson?: string;
|
|
121
113
|
}
|
|
122
114
|
export interface EntityDeletedEvent {
|
|
123
|
-
/** Entity that was deleted */
|
|
115
|
+
/** Entity that was deleted. */
|
|
124
116
|
deletedEntityAsJson?: string | null;
|
|
125
117
|
}
|
|
126
118
|
export interface ActionEvent {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.types.js","sourceRoot":"","sources":["../../../src/ecom-v1-orders-settings-orders-settings.types.ts"],"names":[],"mappings":"AA0BA,MAAM,CAAN,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,KAAtB,sBAAsB,QAMjC;
|
|
1
|
+
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.types.js","sourceRoot":"","sources":["../../../src/ecom-v1-orders-settings-orders-settings.types.ts"],"names":[],"mappings":"AA0BA,MAAM,CAAN,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,KAAtB,sBAAsB,QAMjC;AAuKD,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"}
|
|
@@ -61,25 +61,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
61
61
|
updatedEvent?: EntityUpdatedEvent;
|
|
62
62
|
deletedEvent?: EntityDeletedEvent;
|
|
63
63
|
actionEvent?: ActionEvent;
|
|
64
|
-
/**
|
|
65
|
-
* Unique event ID.
|
|
66
|
-
* Allows clients to ignore duplicate webhooks.
|
|
67
|
-
*/
|
|
64
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
68
65
|
_id?: string;
|
|
69
66
|
/**
|
|
70
|
-
*
|
|
71
|
-
*
|
|
67
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
68
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
72
69
|
*/
|
|
73
70
|
entityFqdn?: string;
|
|
74
71
|
/**
|
|
75
|
-
*
|
|
76
|
-
*
|
|
77
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
72
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
73
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
78
74
|
*/
|
|
79
75
|
slug?: string;
|
|
80
76
|
/** ID of the entity associated with the event. */
|
|
81
77
|
entityId?: string;
|
|
82
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
78
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
83
79
|
eventTime?: Date | null;
|
|
84
80
|
/**
|
|
85
81
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -89,12 +85,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
89
85
|
/** If present, indicates the action that triggered the event. */
|
|
90
86
|
originatedFrom?: string | null;
|
|
91
87
|
/**
|
|
92
|
-
* A sequence number
|
|
93
|
-
*
|
|
94
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
95
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
96
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
97
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
88
|
+
* 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.
|
|
89
|
+
* 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.
|
|
98
90
|
*/
|
|
99
91
|
entityEventSequence?: string | null;
|
|
100
92
|
}
|
|
@@ -120,7 +112,7 @@ export interface EntityUpdatedEvent {
|
|
|
120
112
|
currentEntity?: string;
|
|
121
113
|
}
|
|
122
114
|
export interface EntityDeletedEvent {
|
|
123
|
-
/** Entity that was deleted */
|
|
115
|
+
/** Entity that was deleted. */
|
|
124
116
|
deletedEntity?: string | null;
|
|
125
117
|
}
|
|
126
118
|
export interface ActionEvent {
|
|
@@ -211,25 +203,21 @@ export interface BaseEventMetadata {
|
|
|
211
203
|
identity?: IdentificationData;
|
|
212
204
|
}
|
|
213
205
|
export interface EventMetadata extends BaseEventMetadata {
|
|
214
|
-
/**
|
|
215
|
-
* Unique event ID.
|
|
216
|
-
* Allows clients to ignore duplicate webhooks.
|
|
217
|
-
*/
|
|
206
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
218
207
|
_id?: string;
|
|
219
208
|
/**
|
|
220
|
-
*
|
|
221
|
-
*
|
|
209
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
210
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
222
211
|
*/
|
|
223
212
|
entityFqdn?: string;
|
|
224
213
|
/**
|
|
225
|
-
*
|
|
226
|
-
*
|
|
227
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
214
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
215
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
228
216
|
*/
|
|
229
217
|
slug?: string;
|
|
230
218
|
/** ID of the entity associated with the event. */
|
|
231
219
|
entityId?: string;
|
|
232
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
220
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
233
221
|
eventTime?: Date | null;
|
|
234
222
|
/**
|
|
235
223
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -239,12 +227,8 @@ export interface EventMetadata extends BaseEventMetadata {
|
|
|
239
227
|
/** If present, indicates the action that triggered the event. */
|
|
240
228
|
originatedFrom?: string | null;
|
|
241
229
|
/**
|
|
242
|
-
* A sequence number
|
|
243
|
-
*
|
|
244
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
245
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
246
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
247
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
230
|
+
* 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.
|
|
231
|
+
* 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.
|
|
248
232
|
*/
|
|
249
233
|
entityEventSequence?: string | null;
|
|
250
234
|
}
|
|
@@ -256,6 +240,8 @@ export interface OrdersSettingsUpdatedEnvelope {
|
|
|
256
240
|
* Triggered when orders settings are updated.
|
|
257
241
|
* @permissionScope Manage Stores - all permissions
|
|
258
242
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
243
|
+
* @permissionScope Manage Stores
|
|
244
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
259
245
|
* @permissionScope Read eCommerce - all read permissions
|
|
260
246
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
261
247
|
* @permissionScope Read Orders
|
|
@@ -287,6 +273,8 @@ type OrdersSettingsNonNullablePaths = `inventoryUpdateTrigger`;
|
|
|
287
273
|
* @permissionId ECOM.READ_ORDERS_SETTINGS
|
|
288
274
|
* @permissionScope Manage Stores - all permissions
|
|
289
275
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
276
|
+
* @permissionScope Manage Stores
|
|
277
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
290
278
|
* @permissionScope Read eCommerce - all read permissions
|
|
291
279
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
292
280
|
* @permissionScope Read Orders
|
|
@@ -319,6 +307,8 @@ export declare function getOrdersSettings(): Promise<NonNullablePaths<GetOrdersS
|
|
|
319
307
|
* @permissionId ECOM.UPDATE_ORDERS_SETTINGS
|
|
320
308
|
* @permissionScope Manage Stores - all permissions
|
|
321
309
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
310
|
+
* @permissionScope Manage Stores
|
|
311
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
322
312
|
* @permissionScope Manage Restaurants - all permissions
|
|
323
313
|
* @permissionScopeId SCOPE.RESTAURANTS.MEGA-SCOPES
|
|
324
314
|
* @permissionScope Manage eCommerce - all permissions
|
|
@@ -27,6 +27,8 @@ export var WebhookIdentityType;
|
|
|
27
27
|
* @permissionId ECOM.READ_ORDERS_SETTINGS
|
|
28
28
|
* @permissionScope Manage Stores - all permissions
|
|
29
29
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
30
|
+
* @permissionScope Manage Stores
|
|
31
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
30
32
|
* @permissionScope Read eCommerce - all read permissions
|
|
31
33
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
32
34
|
* @permissionScope Read Orders
|
|
@@ -77,6 +79,8 @@ export async function getOrdersSettings() {
|
|
|
77
79
|
* @permissionId ECOM.UPDATE_ORDERS_SETTINGS
|
|
78
80
|
* @permissionScope Manage Stores - all permissions
|
|
79
81
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
82
|
+
* @permissionScope Manage Stores
|
|
83
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
80
84
|
* @permissionScope Manage Restaurants - all permissions
|
|
81
85
|
* @permissionScopeId SCOPE.RESTAURANTS.MEGA-SCOPES
|
|
82
86
|
* @permissionScope Manage eCommerce - all permissions
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.universal.js","sourceRoot":"","sources":["../../../src/ecom-v1-orders-settings-orders-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,iCAAiC,MAAM,mDAAmD,CAAC;AA6BvG,MAAM,CAAN,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,KAAtB,sBAAsB,QAMjC;
|
|
1
|
+
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.universal.js","sourceRoot":"","sources":["../../../src/ecom-v1-orders-settings-orders-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,iCAAiC,MAAM,mDAAmD,CAAC;AA6BvG,MAAM,CAAN,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,KAAtB,sBAAsB,QAMjC;AAqKD,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;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB;IAQrC,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,GAAG,iCAAiC,CAAC,iBAAiB,CAAC,OAAO,CAAC,CAAC;IAE7E,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,CAAC,MAAM,CAAC,IAAI,CAAE,CAAC;IAC/D,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;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,CAAC,KAAK,UAAU,oBAAoB,CACxC,cAA8B;IAS9B,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,qCAAqC,CAAC;QACpD,cAAc,EAAE,cAAc;KAC/B,CAAC,CAAC;IAEH,MAAM,OAAO,GACX,iCAAiC,CAAC,oBAAoB,CAAC,OAAO,CAAC,CAAC;IAElE,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,CAAC,MAAM,CAAC,IAAI,CAAE,CAAC;IAC/D,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,iBAAiB,CACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE,cAAc,EAAE,MAAM,EAAE;YACpD,uBAAuB,EAAE,KAAK;SAC/B,EACD,CAAC,gBAAgB,CAAC,CACnB,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC"}
|
|
@@ -59,25 +59,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
59
59
|
updatedEvent?: EntityUpdatedEvent;
|
|
60
60
|
deletedEvent?: EntityDeletedEvent;
|
|
61
61
|
actionEvent?: ActionEvent;
|
|
62
|
-
/**
|
|
63
|
-
* Unique event ID.
|
|
64
|
-
* Allows clients to ignore duplicate webhooks.
|
|
65
|
-
*/
|
|
62
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
66
63
|
id?: string;
|
|
67
64
|
/**
|
|
68
|
-
*
|
|
69
|
-
*
|
|
65
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
66
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
70
67
|
*/
|
|
71
68
|
entityFqdn?: string;
|
|
72
69
|
/**
|
|
73
|
-
*
|
|
74
|
-
*
|
|
75
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
70
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
71
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
76
72
|
*/
|
|
77
73
|
slug?: string;
|
|
78
74
|
/** ID of the entity associated with the event. */
|
|
79
75
|
entityId?: string;
|
|
80
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
76
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
81
77
|
eventTime?: Date | null;
|
|
82
78
|
/**
|
|
83
79
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -87,12 +83,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
87
83
|
/** If present, indicates the action that triggered the event. */
|
|
88
84
|
originatedFrom?: string | null;
|
|
89
85
|
/**
|
|
90
|
-
* A sequence number
|
|
91
|
-
*
|
|
92
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
93
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
94
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
95
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
86
|
+
* 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.
|
|
87
|
+
* 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.
|
|
96
88
|
*/
|
|
97
89
|
entityEventSequence?: string | null;
|
|
98
90
|
}
|
|
@@ -120,7 +112,7 @@ export interface EntityUpdatedEvent {
|
|
|
120
112
|
currentEntityAsJson?: string;
|
|
121
113
|
}
|
|
122
114
|
export interface EntityDeletedEvent {
|
|
123
|
-
/** Entity that was deleted */
|
|
115
|
+
/** Entity that was deleted. */
|
|
124
116
|
deletedEntityAsJson?: string | null;
|
|
125
117
|
}
|
|
126
118
|
export interface ActionEvent {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.types.js","sourceRoot":"","sources":["../../../../src/ecom-v1-orders-settings-orders-settings.types.ts"],"names":[],"mappings":";;;AA0BA,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,sCAAtB,sBAAsB,QAMjC;
|
|
1
|
+
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.types.js","sourceRoot":"","sources":["../../../../src/ecom-v1-orders-settings-orders-settings.types.ts"],"names":[],"mappings":";;;AA0BA,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,sCAAtB,sBAAsB,QAMjC;AAuKD,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"}
|
|
@@ -61,25 +61,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
61
61
|
updatedEvent?: EntityUpdatedEvent;
|
|
62
62
|
deletedEvent?: EntityDeletedEvent;
|
|
63
63
|
actionEvent?: ActionEvent;
|
|
64
|
-
/**
|
|
65
|
-
* Unique event ID.
|
|
66
|
-
* Allows clients to ignore duplicate webhooks.
|
|
67
|
-
*/
|
|
64
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
68
65
|
_id?: string;
|
|
69
66
|
/**
|
|
70
|
-
*
|
|
71
|
-
*
|
|
67
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
68
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
72
69
|
*/
|
|
73
70
|
entityFqdn?: string;
|
|
74
71
|
/**
|
|
75
|
-
*
|
|
76
|
-
*
|
|
77
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
72
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
73
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
78
74
|
*/
|
|
79
75
|
slug?: string;
|
|
80
76
|
/** ID of the entity associated with the event. */
|
|
81
77
|
entityId?: string;
|
|
82
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
78
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
83
79
|
eventTime?: Date | null;
|
|
84
80
|
/**
|
|
85
81
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -89,12 +85,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
89
85
|
/** If present, indicates the action that triggered the event. */
|
|
90
86
|
originatedFrom?: string | null;
|
|
91
87
|
/**
|
|
92
|
-
* A sequence number
|
|
93
|
-
*
|
|
94
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
95
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
96
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
97
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
88
|
+
* 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.
|
|
89
|
+
* 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.
|
|
98
90
|
*/
|
|
99
91
|
entityEventSequence?: string | null;
|
|
100
92
|
}
|
|
@@ -120,7 +112,7 @@ export interface EntityUpdatedEvent {
|
|
|
120
112
|
currentEntity?: string;
|
|
121
113
|
}
|
|
122
114
|
export interface EntityDeletedEvent {
|
|
123
|
-
/** Entity that was deleted */
|
|
115
|
+
/** Entity that was deleted. */
|
|
124
116
|
deletedEntity?: string | null;
|
|
125
117
|
}
|
|
126
118
|
export interface ActionEvent {
|
|
@@ -211,25 +203,21 @@ export interface BaseEventMetadata {
|
|
|
211
203
|
identity?: IdentificationData;
|
|
212
204
|
}
|
|
213
205
|
export interface EventMetadata extends BaseEventMetadata {
|
|
214
|
-
/**
|
|
215
|
-
* Unique event ID.
|
|
216
|
-
* Allows clients to ignore duplicate webhooks.
|
|
217
|
-
*/
|
|
206
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
218
207
|
_id?: string;
|
|
219
208
|
/**
|
|
220
|
-
*
|
|
221
|
-
*
|
|
209
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
210
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
222
211
|
*/
|
|
223
212
|
entityFqdn?: string;
|
|
224
213
|
/**
|
|
225
|
-
*
|
|
226
|
-
*
|
|
227
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
214
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
215
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
228
216
|
*/
|
|
229
217
|
slug?: string;
|
|
230
218
|
/** ID of the entity associated with the event. */
|
|
231
219
|
entityId?: string;
|
|
232
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
220
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
233
221
|
eventTime?: Date | null;
|
|
234
222
|
/**
|
|
235
223
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -239,12 +227,8 @@ export interface EventMetadata extends BaseEventMetadata {
|
|
|
239
227
|
/** If present, indicates the action that triggered the event. */
|
|
240
228
|
originatedFrom?: string | null;
|
|
241
229
|
/**
|
|
242
|
-
* A sequence number
|
|
243
|
-
*
|
|
244
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
245
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
246
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
247
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
230
|
+
* 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.
|
|
231
|
+
* 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.
|
|
248
232
|
*/
|
|
249
233
|
entityEventSequence?: string | null;
|
|
250
234
|
}
|
|
@@ -256,6 +240,8 @@ export interface OrdersSettingsUpdatedEnvelope {
|
|
|
256
240
|
* Triggered when orders settings are updated.
|
|
257
241
|
* @permissionScope Manage Stores - all permissions
|
|
258
242
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
243
|
+
* @permissionScope Manage Stores
|
|
244
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
259
245
|
* @permissionScope Read eCommerce - all read permissions
|
|
260
246
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
261
247
|
* @permissionScope Read Orders
|
|
@@ -287,6 +273,8 @@ type OrdersSettingsNonNullablePaths = `inventoryUpdateTrigger`;
|
|
|
287
273
|
* @permissionId ECOM.READ_ORDERS_SETTINGS
|
|
288
274
|
* @permissionScope Manage Stores - all permissions
|
|
289
275
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
276
|
+
* @permissionScope Manage Stores
|
|
277
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
290
278
|
* @permissionScope Read eCommerce - all read permissions
|
|
291
279
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
292
280
|
* @permissionScope Read Orders
|
|
@@ -319,6 +307,8 @@ export declare function getOrdersSettings(): Promise<NonNullablePaths<GetOrdersS
|
|
|
319
307
|
* @permissionId ECOM.UPDATE_ORDERS_SETTINGS
|
|
320
308
|
* @permissionScope Manage Stores - all permissions
|
|
321
309
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
310
|
+
* @permissionScope Manage Stores
|
|
311
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
322
312
|
* @permissionScope Manage Restaurants - all permissions
|
|
323
313
|
* @permissionScopeId SCOPE.RESTAURANTS.MEGA-SCOPES
|
|
324
314
|
* @permissionScope Manage eCommerce - all permissions
|
|
@@ -53,6 +53,8 @@ var WebhookIdentityType;
|
|
|
53
53
|
* @permissionId ECOM.READ_ORDERS_SETTINGS
|
|
54
54
|
* @permissionScope Manage Stores - all permissions
|
|
55
55
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
56
|
+
* @permissionScope Manage Stores
|
|
57
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
56
58
|
* @permissionScope Read eCommerce - all read permissions
|
|
57
59
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
58
60
|
* @permissionScope Read Orders
|
|
@@ -104,6 +106,8 @@ exports.getOrdersSettings = getOrdersSettings;
|
|
|
104
106
|
* @permissionId ECOM.UPDATE_ORDERS_SETTINGS
|
|
105
107
|
* @permissionScope Manage Stores - all permissions
|
|
106
108
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
109
|
+
* @permissionScope Manage Stores
|
|
110
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
107
111
|
* @permissionScope Manage Restaurants - all permissions
|
|
108
112
|
* @permissionScopeId SCOPE.RESTAURANTS.MEGA-SCOPES
|
|
109
113
|
* @permissionScope Manage eCommerce - all permissions
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.universal.js","sourceRoot":"","sources":["../../../../src/ecom-v1-orders-settings-orders-settings.universal.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,sEAAuF;AACvF,oFAGiD;AAEjD,qHAAuG;AA6BvG,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,sCAAtB,sBAAsB,QAMjC;
|
|
1
|
+
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.universal.js","sourceRoot":"","sources":["../../../../src/ecom-v1-orders-settings-orders-settings.universal.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,sEAAuF;AACvF,oFAGiD;AAEjD,qHAAuG;AA6BvG,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,sCAAtB,sBAAsB,QAMjC;AAqKD,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;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACI,KAAK,UAAU,iBAAiB;IAQrC,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,GAAG,iCAAiC,CAAC,iBAAiB,CAAC,OAAO,CAAC,CAAC;IAE7E,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,EAAC,MAAM,CAAC,IAAI,CAAE,CAAC;IAC/D,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;AAtCD,8CAsCC;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACI,KAAK,UAAU,oBAAoB,CACxC,cAA8B;IAS9B,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,IAAA,8DAAqC,EAAC;QACpD,cAAc,EAAE,cAAc;KAC/B,CAAC,CAAC;IAEH,MAAM,OAAO,GACX,iCAAiC,CAAC,oBAAoB,CAAC,OAAO,CAAC,CAAC;IAElE,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,EAAC,MAAM,CAAC,IAAI,CAAE,CAAC;IAC/D,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,IAAA,gCAAiB,EACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE,cAAc,EAAE,MAAM,EAAE;YACpD,uBAAuB,EAAE,KAAK;SAC/B,EACD,CAAC,gBAAgB,CAAC,CACnB,CAAC;QACF,WAAW,EAAE,OAAO,EAAE,CAAC,GAAG,CAAC,CAAC;QAE5B,MAAM,gBAAgB,CAAC;IACzB,CAAC;AACH,CAAC;AA3CD,oDA2CC"}
|
|
@@ -59,25 +59,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
59
59
|
updatedEvent?: EntityUpdatedEvent;
|
|
60
60
|
deletedEvent?: EntityDeletedEvent;
|
|
61
61
|
actionEvent?: ActionEvent;
|
|
62
|
-
/**
|
|
63
|
-
* Unique event ID.
|
|
64
|
-
* Allows clients to ignore duplicate webhooks.
|
|
65
|
-
*/
|
|
62
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
66
63
|
id?: string;
|
|
67
64
|
/**
|
|
68
|
-
*
|
|
69
|
-
*
|
|
65
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
66
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
70
67
|
*/
|
|
71
68
|
entityFqdn?: string;
|
|
72
69
|
/**
|
|
73
|
-
*
|
|
74
|
-
*
|
|
75
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
70
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
71
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
76
72
|
*/
|
|
77
73
|
slug?: string;
|
|
78
74
|
/** ID of the entity associated with the event. */
|
|
79
75
|
entityId?: string;
|
|
80
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
76
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
81
77
|
eventTime?: Date | null;
|
|
82
78
|
/**
|
|
83
79
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -87,12 +83,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
87
83
|
/** If present, indicates the action that triggered the event. */
|
|
88
84
|
originatedFrom?: string | null;
|
|
89
85
|
/**
|
|
90
|
-
* A sequence number
|
|
91
|
-
*
|
|
92
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
93
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
94
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
95
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
86
|
+
* 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.
|
|
87
|
+
* 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.
|
|
96
88
|
*/
|
|
97
89
|
entityEventSequence?: string | null;
|
|
98
90
|
}
|
|
@@ -120,7 +112,7 @@ export interface EntityUpdatedEvent {
|
|
|
120
112
|
currentEntityAsJson?: string;
|
|
121
113
|
}
|
|
122
114
|
export interface EntityDeletedEvent {
|
|
123
|
-
/** Entity that was deleted */
|
|
115
|
+
/** Entity that was deleted. */
|
|
124
116
|
deletedEntityAsJson?: string | null;
|
|
125
117
|
}
|
|
126
118
|
export interface ActionEvent {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.types.js","sourceRoot":"","sources":["../../../../src/ecom-v1-orders-settings-orders-settings.types.ts"],"names":[],"mappings":"AA0BA,MAAM,CAAN,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,KAAtB,sBAAsB,QAMjC;
|
|
1
|
+
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.types.js","sourceRoot":"","sources":["../../../../src/ecom-v1-orders-settings-orders-settings.types.ts"],"names":[],"mappings":"AA0BA,MAAM,CAAN,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,KAAtB,sBAAsB,QAMjC;AAuKD,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"}
|
|
@@ -61,25 +61,21 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
61
61
|
updatedEvent?: EntityUpdatedEvent;
|
|
62
62
|
deletedEvent?: EntityDeletedEvent;
|
|
63
63
|
actionEvent?: ActionEvent;
|
|
64
|
-
/**
|
|
65
|
-
* Unique event ID.
|
|
66
|
-
* Allows clients to ignore duplicate webhooks.
|
|
67
|
-
*/
|
|
64
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
68
65
|
_id?: string;
|
|
69
66
|
/**
|
|
70
|
-
*
|
|
71
|
-
*
|
|
67
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
68
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
72
69
|
*/
|
|
73
70
|
entityFqdn?: string;
|
|
74
71
|
/**
|
|
75
|
-
*
|
|
76
|
-
*
|
|
77
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
72
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
73
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
78
74
|
*/
|
|
79
75
|
slug?: string;
|
|
80
76
|
/** ID of the entity associated with the event. */
|
|
81
77
|
entityId?: string;
|
|
82
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
78
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
83
79
|
eventTime?: Date | null;
|
|
84
80
|
/**
|
|
85
81
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -89,12 +85,8 @@ export interface DomainEvent extends DomainEventBodyOneOf {
|
|
|
89
85
|
/** If present, indicates the action that triggered the event. */
|
|
90
86
|
originatedFrom?: string | null;
|
|
91
87
|
/**
|
|
92
|
-
* A sequence number
|
|
93
|
-
*
|
|
94
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
95
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
96
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
97
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
88
|
+
* 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.
|
|
89
|
+
* 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.
|
|
98
90
|
*/
|
|
99
91
|
entityEventSequence?: string | null;
|
|
100
92
|
}
|
|
@@ -120,7 +112,7 @@ export interface EntityUpdatedEvent {
|
|
|
120
112
|
currentEntity?: string;
|
|
121
113
|
}
|
|
122
114
|
export interface EntityDeletedEvent {
|
|
123
|
-
/** Entity that was deleted */
|
|
115
|
+
/** Entity that was deleted. */
|
|
124
116
|
deletedEntity?: string | null;
|
|
125
117
|
}
|
|
126
118
|
export interface ActionEvent {
|
|
@@ -211,25 +203,21 @@ export interface BaseEventMetadata {
|
|
|
211
203
|
identity?: IdentificationData;
|
|
212
204
|
}
|
|
213
205
|
export interface EventMetadata extends BaseEventMetadata {
|
|
214
|
-
/**
|
|
215
|
-
* Unique event ID.
|
|
216
|
-
* Allows clients to ignore duplicate webhooks.
|
|
217
|
-
*/
|
|
206
|
+
/** Event ID. With this ID you can easily spot duplicated events and ignore them. */
|
|
218
207
|
_id?: string;
|
|
219
208
|
/**
|
|
220
|
-
*
|
|
221
|
-
*
|
|
209
|
+
* Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
|
|
210
|
+
* For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
|
|
222
211
|
*/
|
|
223
212
|
entityFqdn?: string;
|
|
224
213
|
/**
|
|
225
|
-
*
|
|
226
|
-
*
|
|
227
|
-
* Example: created/updated/deleted/started/completed/email_opened
|
|
214
|
+
* Event action name, placed at the top level to make it easier for users to dispatch messages.
|
|
215
|
+
* For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.
|
|
228
216
|
*/
|
|
229
217
|
slug?: string;
|
|
230
218
|
/** ID of the entity associated with the event. */
|
|
231
219
|
entityId?: string;
|
|
232
|
-
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example
|
|
220
|
+
/** Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`. */
|
|
233
221
|
eventTime?: Date | null;
|
|
234
222
|
/**
|
|
235
223
|
* Whether the event was triggered as a result of a privacy regulation application
|
|
@@ -239,12 +227,8 @@ export interface EventMetadata extends BaseEventMetadata {
|
|
|
239
227
|
/** If present, indicates the action that triggered the event. */
|
|
240
228
|
originatedFrom?: string | null;
|
|
241
229
|
/**
|
|
242
|
-
* A sequence number
|
|
243
|
-
*
|
|
244
|
-
* it is guaranteed that the sequence number of the second update is strictly higher than the first.
|
|
245
|
-
* As the consumer, you can use this value to ensure that you handle messages in the correct order.
|
|
246
|
-
* To do so, you will need to persist this number on your end, and compare the sequence number from the
|
|
247
|
-
* message against the one you have stored. Given that the stored number is higher, you should ignore the message.
|
|
230
|
+
* 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.
|
|
231
|
+
* 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.
|
|
248
232
|
*/
|
|
249
233
|
entityEventSequence?: string | null;
|
|
250
234
|
}
|
|
@@ -256,6 +240,8 @@ export interface OrdersSettingsUpdatedEnvelope {
|
|
|
256
240
|
* Triggered when orders settings are updated.
|
|
257
241
|
* @permissionScope Manage Stores - all permissions
|
|
258
242
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
243
|
+
* @permissionScope Manage Stores
|
|
244
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
259
245
|
* @permissionScope Read eCommerce - all read permissions
|
|
260
246
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
261
247
|
* @permissionScope Read Orders
|
|
@@ -287,6 +273,8 @@ type OrdersSettingsNonNullablePaths = `inventoryUpdateTrigger`;
|
|
|
287
273
|
* @permissionId ECOM.READ_ORDERS_SETTINGS
|
|
288
274
|
* @permissionScope Manage Stores - all permissions
|
|
289
275
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
276
|
+
* @permissionScope Manage Stores
|
|
277
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
290
278
|
* @permissionScope Read eCommerce - all read permissions
|
|
291
279
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
292
280
|
* @permissionScope Read Orders
|
|
@@ -319,6 +307,8 @@ export declare function getOrdersSettings(): Promise<NonNullablePaths<GetOrdersS
|
|
|
319
307
|
* @permissionId ECOM.UPDATE_ORDERS_SETTINGS
|
|
320
308
|
* @permissionScope Manage Stores - all permissions
|
|
321
309
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
310
|
+
* @permissionScope Manage Stores
|
|
311
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
322
312
|
* @permissionScope Manage Restaurants - all permissions
|
|
323
313
|
* @permissionScopeId SCOPE.RESTAURANTS.MEGA-SCOPES
|
|
324
314
|
* @permissionScope Manage eCommerce - all permissions
|
|
@@ -27,6 +27,8 @@ export var WebhookIdentityType;
|
|
|
27
27
|
* @permissionId ECOM.READ_ORDERS_SETTINGS
|
|
28
28
|
* @permissionScope Manage Stores - all permissions
|
|
29
29
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
30
|
+
* @permissionScope Manage Stores
|
|
31
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
30
32
|
* @permissionScope Read eCommerce - all read permissions
|
|
31
33
|
* @permissionScopeId SCOPE.DC-ECOM-MEGA.READ-ECOM
|
|
32
34
|
* @permissionScope Read Orders
|
|
@@ -77,6 +79,8 @@ export async function getOrdersSettings() {
|
|
|
77
79
|
* @permissionId ECOM.UPDATE_ORDERS_SETTINGS
|
|
78
80
|
* @permissionScope Manage Stores - all permissions
|
|
79
81
|
* @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
|
|
82
|
+
* @permissionScope Manage Stores
|
|
83
|
+
* @permissionScopeId SCOPE.STORES.MANAGE-STORES
|
|
80
84
|
* @permissionScope Manage Restaurants - all permissions
|
|
81
85
|
* @permissionScopeId SCOPE.RESTAURANTS.MEGA-SCOPES
|
|
82
86
|
* @permissionScope Manage eCommerce - all permissions
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.universal.js","sourceRoot":"","sources":["../../../../src/ecom-v1-orders-settings-orders-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,iCAAiC,MAAM,mDAAmD,CAAC;AA6BvG,MAAM,CAAN,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,KAAtB,sBAAsB,QAMjC;
|
|
1
|
+
{"version":3,"file":"ecom-v1-orders-settings-orders-settings.universal.js","sourceRoot":"","sources":["../../../../src/ecom-v1-orders-settings-orders-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,iCAAiC,MAAM,mDAAmD,CAAC;AA6BvG,MAAM,CAAN,IAAY,sBAMX;AAND,WAAY,sBAAsB;IAChC,+FAAqE,CAAA;IACrE,uEAAuE;IACvE,yDAA+B,CAAA;IAC/B,gIAAgI;IAChI,6DAAmC,CAAA;AACrC,CAAC,EANW,sBAAsB,KAAtB,sBAAsB,QAMjC;AAqKD,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;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB;IAQrC,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,GAAG,iCAAiC,CAAC,iBAAiB,CAAC,OAAO,CAAC,CAAC;IAE7E,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,CAAC,MAAM,CAAC,IAAI,CAAE,CAAC;IAC/D,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;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,CAAC,KAAK,UAAU,oBAAoB,CACxC,cAA8B;IAS9B,aAAa;IACb,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,GAAG,SAAS,CAAC,CAAC,CAG9C,CAAC;IAEF,MAAM,OAAO,GAAG,qCAAqC,CAAC;QACpD,cAAc,EAAE,cAAc;KAC/B,CAAC,CAAC;IAEH,MAAM,OAAO,GACX,iCAAiC,CAAC,oBAAoB,CAAC,OAAO,CAAC,CAAC;IAElE,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,CAAC,MAAM,CAAC,IAAI,CAAE,CAAC;IAC/D,CAAC;IAAC,OAAO,GAAQ,EAAE,CAAC;QAClB,MAAM,gBAAgB,GAAG,iBAAiB,CACxC,GAAG,EACH;YACE,sBAAsB,EAAE,EAAE;YAC1B,wBAAwB,EAAE,EAAE,cAAc,EAAE,MAAM,EAAE;YACpD,uBAAuB,EAAE,KAAK;SAC/B,EACD,CAAC,gBAAgB,CAAC,CACnB,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_orders-settings",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.9",
|
|
4
4
|
"publishConfig": {
|
|
5
5
|
"registry": "https://registry.npmjs.org/",
|
|
6
6
|
"access": "public"
|
|
@@ -48,5 +48,5 @@
|
|
|
48
48
|
"fqdn": "wix.ecom.v1.orders_settings"
|
|
49
49
|
}
|
|
50
50
|
},
|
|
51
|
-
"falconPackageHash": "
|
|
51
|
+
"falconPackageHash": "0208926cdff740e73f7342ac93100dc89b6c45d1486dfceef6e2bcb3"
|
|
52
52
|
}
|