@wix/auto_sdk_ecom_order-transactions 1.0.88 → 1.0.89

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.
@@ -1511,7 +1511,7 @@ interface DomainEvent extends DomainEventBodyOneOf {
1511
1511
  /** If present, indicates the action that triggered the event. */
1512
1512
  originatedFrom?: string | null;
1513
1513
  /**
1514
- * 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.
1514
+ * 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.
1515
1515
  * 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.
1516
1516
  */
1517
1517
  entityEventSequence?: string | null;
@@ -1700,7 +1700,7 @@ interface EventMetadata extends BaseEventMetadata {
1700
1700
  /** If present, indicates the action that triggered the event. */
1701
1701
  originatedFrom?: string | null;
1702
1702
  /**
1703
- * 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.
1703
+ * 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.
1704
1704
  * 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.
1705
1705
  */
1706
1706
  entityEventSequence?: string | null;