@wix/auto_sdk_restaurants_item-modifier-groups 1.0.70 → 1.0.72

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.
Files changed (33) hide show
  1. package/build/cjs/index.d.ts +9 -27
  2. package/build/cjs/index.js +32 -806
  3. package/build/cjs/index.js.map +1 -1
  4. package/build/cjs/index.typings.d.ts +2 -2
  5. package/build/cjs/index.typings.js +10 -784
  6. package/build/cjs/index.typings.js.map +1 -1
  7. package/build/cjs/meta.d.ts +1 -1
  8. package/build/cjs/meta.js.map +1 -1
  9. package/build/es/index.d.mts +9 -27
  10. package/build/es/index.mjs +32 -796
  11. package/build/es/index.mjs.map +1 -1
  12. package/build/es/index.typings.d.mts +2 -2
  13. package/build/es/index.typings.mjs +10 -774
  14. package/build/es/index.typings.mjs.map +1 -1
  15. package/build/es/meta.d.mts +1 -1
  16. package/build/es/meta.mjs.map +1 -1
  17. package/build/internal/cjs/index.d.ts +9 -27
  18. package/build/internal/cjs/index.js +32 -806
  19. package/build/internal/cjs/index.js.map +1 -1
  20. package/build/internal/cjs/index.typings.d.ts +2 -2
  21. package/build/internal/cjs/index.typings.js +10 -784
  22. package/build/internal/cjs/index.typings.js.map +1 -1
  23. package/build/internal/cjs/meta.d.ts +1 -1
  24. package/build/internal/cjs/meta.js.map +1 -1
  25. package/build/internal/es/index.d.mts +9 -27
  26. package/build/internal/es/index.mjs +32 -796
  27. package/build/internal/es/index.mjs.map +1 -1
  28. package/build/internal/es/index.typings.d.mts +2 -2
  29. package/build/internal/es/index.typings.mjs +10 -774
  30. package/build/internal/es/index.typings.mjs.map +1 -1
  31. package/build/internal/es/meta.d.mts +1 -1
  32. package/build/internal/es/meta.mjs.map +1 -1
  33. package/package.json +2 -2
package/build/cjs/index.typings.d.ts CHANGED
@@ -659,7 +659,7 @@ interface DomainEvent extends DomainEventBodyOneOf {
659
659
  /** If present, indicates the action that triggered the event. */
660
660
  originatedFrom?: string | null;
661
661
  /**
662
- * 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.
662
+ * 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.
663
663
  * 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.
664
664
  */
665
665
  entityEventSequence?: string | null;
@@ -841,7 +841,7 @@ interface EventMetadata extends BaseEventMetadata {
841
841
  /** If present, indicates the action that triggered the event. */
842
842
  originatedFrom?: string | null;
843
843
  /**
844
- * 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.
844
+ * 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.
845
845
  * 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.
846
846
  */
847
847
  entityEventSequence?: string | null;