@wix/auto_sdk_restaurants_fulfillment-methods 1.0.68 → 1.0.69

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.
@@ -410,7 +410,7 @@ interface DomainEvent extends DomainEventBodyOneOf {
410
410
  /** If present, indicates the action that triggered the event. */
411
411
  originatedFrom?: string | null;
412
412
  /**
413
- * 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.
413
+ * 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.
414
414
  * 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.
415
415
  */
416
416
  entityEventSequence?: string | null;
@@ -1410,7 +1410,7 @@ interface EventMetadata extends BaseEventMetadata {
1410
1410
  /** If present, indicates the action that triggered the event. */
1411
1411
  originatedFrom?: string | null;
1412
1412
  /**
1413
- * 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.
1413
+ * 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.
1414
1414
  * 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.
1415
1415
  */
1416
1416
  entityEventSequence?: string | null;
@@ -1780,7 +1780,10 @@ declare const utils: {
1780
1780
  query: {
1781
1781
  QueryBuilder: () => _wix_sdk_types.QueryBuilder<FulfillmentMethod, FulfillmentMethodQuerySpec, FulfillmentMethodQuery>;
1782
1782
  Filter: _wix_sdk_types.FilterFactory<FulfillmentMethod, FulfillmentMethodQuerySpec>;
1783
- Sort: _wix_sdk_types.SortFactory<FulfillmentMethodQuerySpec>;
1783
+ Sort: _wix_sdk_types.SortFactory<FulfillmentMethodQuerySpec>; /**
1784
+ * Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
1785
+ * For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.
1786
+ */
1784
1787
  };
1785
1788
  };
1786
1789
  /**