@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.
@@ -947,7 +947,7 @@ interface DomainEvent extends DomainEventBodyOneOf {
947
947
  /** If present, indicates the action that triggered the event. */
948
948
  originatedFrom?: string | null;
949
949
  /**
950
- * A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at 16:00 and then again at 16:01, the second update will always have a higher sequence number.
950
+ * A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at `16:00` and then again at `16:01`, the second update will always have a higher sequence number.
951
951
  * You can use this number to make sure you're handling updates in the right order. Just save the latest sequence number on your end and compare it to the one in each new message. If the new message has an older (lower) number, you can safely ignore it.
952
952
  */
953
953
  entityEventSequence?: string | null;
@@ -1323,7 +1323,7 @@ interface EventMetadata extends BaseEventMetadata {
1323
1323
  /** If present, indicates the action that triggered the event. */
1324
1324
  originatedFrom?: string | null;
1325
1325
  /**
1326
- * A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at 16:00 and then again at 16:01, the second update will always have a higher sequence number.
1326
+ * A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at `16:00` and then again at `16:01`, the second update will always have a higher sequence number.
1327
1327
  * You can use this number to make sure you're handling updates in the right order. Just save the latest sequence number on your end and compare it to the one in each new message. If the new message has an older (lower) number, you can safely ignore it.
1328
1328
  */
1329
1329
  entityEventSequence?: string | null;
@@ -1345,6 +1345,8 @@ interface CustomizationCreatedEnvelope {
1345
1345
  * Triggered when a customization is created.
1346
1346
  * @permissionScope Manage Stores - all permissions
1347
1347
  * @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
1348
+ * @permissionScope Manage_Wix_Rentals_App_Forms_submissions
1349
+ * @permissionScopeId SCOPE.RENTALS.MANAGE
1348
1350
  * @permissionScope Manage Stores
1349
1351
  * @permissionScopeId SCOPE.STORES.MANAGE-STORES
1350
1352
  * @permissionScope Read customizations in v3 catalog (PII)
@@ -1384,6 +1386,8 @@ interface CustomizationDeletedEnvelope {
1384
1386
  * Triggered when a customization is deleted.
1385
1387
  * @permissionScope Manage Stores - all permissions
1386
1388
  * @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
1389
+ * @permissionScope Manage_Wix_Rentals_App_Forms_submissions
1390
+ * @permissionScopeId SCOPE.RENTALS.MANAGE
1387
1391
  * @permissionScope Manage Stores
1388
1392
  * @permissionScopeId SCOPE.STORES.MANAGE-STORES
1389
1393
  * @permissionScope Read customizations in v3 catalog (PII)
@@ -1425,6 +1429,8 @@ interface CustomizationUpdatedEnvelope {
1425
1429
  * Triggered when a customization is updated.
1426
1430
  * @permissionScope Manage Stores - all permissions
1427
1431
  * @permissionScopeId SCOPE.DC-STORES-MEGA.MANAGE-STORES
1432
+ * @permissionScope Manage_Wix_Rentals_App_Forms_submissions
1433
+ * @permissionScopeId SCOPE.RENTALS.MANAGE
1428
1434
  * @permissionScope Manage Stores
1429
1435
  * @permissionScopeId SCOPE.STORES.MANAGE-STORES
1430
1436
  * @permissionScope Read customizations in v3 catalog (PII)