@wix/auto_sdk_stores_customizations-v-3 1.0.84 → 1.0.86

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.
@@ -939,7 +939,7 @@ interface DomainEvent extends DomainEventBodyOneOf {
939
939
  /** If present, indicates the action that triggered the event. */
940
940
  originatedFrom?: string | null;
941
941
  /**
942
- * A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at 16:00 and then again at 16:01, the second update will always have a higher sequence number.
942
+ * A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at `16:00` and then again at `16:01`, the second update will always have a higher sequence number.
943
943
  * You can use this number to make sure you're handling updates in the right order. Just save the latest sequence number on your end and compare it to the one in each new message. If the new message has an older (lower) number, you can safely ignore it.
944
944
  */
945
945
  entityEventSequence?: string | null;
@@ -1315,7 +1315,7 @@ interface EventMetadata extends BaseEventMetadata {
1315
1315
  /** If present, indicates the action that triggered the event. */
1316
1316
  originatedFrom?: string | null;
1317
1317
  /**
1318
- * A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at 16:00 and then again at 16:01, the second update will always have a higher sequence number.
1318
+ * A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at `16:00` and then again at `16:01`, the second update will always have a higher sequence number.
1319
1319
  * You can use this number to make sure you're handling updates in the right order. Just save the latest sequence number on your end and compare it to the one in each new message. If the new message has an older (lower) number, you can safely ignore it.
1320
1320
  */
1321
1321
  entityEventSequence?: string | null;
@@ -1337,6 +1337,8 @@ interface CustomizationCreatedEnvelope {
1337
1337
  * Triggered when a customization is created.
1338
1338
  * @permissionScope Manage Stores - all permissions
1339
1339
  * @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
1340
+ * @permissionScope Manage_Wix_Rentals_App_Forms_submissions
1341
+ * @permissionScopeId SCOPE.RENTALS.MANAGE
1340
1342
  * @permissionScope Manage Stores
1341
1343
  * @permissionScopeId SCOPE.STORES.MANAGE-STORES
1342
1344
  * @permissionScope Read customizations in v3 catalog (PII)
@@ -1376,6 +1378,8 @@ interface CustomizationDeletedEnvelope {
1376
1378
  * Triggered when a customization is deleted.
1377
1379
  * @permissionScope Manage Stores - all permissions
1378
1380
  * @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
1381
+ * @permissionScope Manage_Wix_Rentals_App_Forms_submissions
1382
+ * @permissionScopeId SCOPE.RENTALS.MANAGE
1379
1383
  * @permissionScope Manage Stores
1380
1384
  * @permissionScopeId SCOPE.STORES.MANAGE-STORES
1381
1385
  * @permissionScope Read customizations in v3 catalog (PII)
@@ -1417,6 +1421,8 @@ interface CustomizationUpdatedEnvelope {
1417
1421
  * Triggered when a customization is updated.
1418
1422
  * @permissionScope Manage Stores - all permissions
1419
1423
  * @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
1424
+ * @permissionScope Manage_Wix_Rentals_App_Forms_submissions
1425
+ * @permissionScopeId SCOPE.RENTALS.MANAGE
1420
1426
  * @permissionScope Manage Stores
1421
1427
  * @permissionScopeId SCOPE.STORES.MANAGE-STORES
1422
1428
  * @permissionScope Read customizations in v3 catalog (PII)