@wix/events 1.0.346 → 1.0.347

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/events",
-  "version": "1.0.346",
+  "version": "1.0.347",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"
@@ -27,7 +27,7 @@
     "@wix/events_notifications": "1.0.43",
     "@wix/events_orders": "1.0.62",
     "@wix/events_policies": "1.0.49",
-    "@wix/events_ricos": "1.0.21",
+    "@wix/events_ricos": "1.0.22",
     "@wix/events_rsvp": "1.0.53",
     "@wix/events_rsvp-v-2": "1.0.24",
     "@wix/events_schedule": "1.0.47",
@@ -61,5 +61,5 @@
       "fqdn": ""
     }
   },
-  "falconPackageHash": "3eb0047d59a8a11ddd8a8d5636a1b3a581efc8bc1ba5b308d150dba1"
+  "falconPackageHash": "6f0695d23d7f9d22e40fb43233b452fe339e71c648437cd04a0041d9"
 }

package/type-bundles/context.bundle.d.ts

@@ -13008,15 +13008,20 @@ interface QueryRichContentsSignature {
 declare function queryRichContent$1(httpClient: HttpClient): QueryRichContentSignature;
 interface QueryRichContentSignature {
     /**
-     * Retrieves a list of rich content entities, given the provided paging, filtering, and sorting.
+     * Creates a query to retrieve a list of rich content entities.
      *
-     * Query Rich Content runs with these defaults, which you can override:
-     * - `createdDate` is sorted in `ASC` order
-     * - `paging.limit` is `100`
-     * - `paging.offset` is `0`
+     * The `queryRichContent()` function builds a query to retrieve a list of events and returns a `RichContentQueryBuilder` object.
+     *
+     * The returned object contains the query definition, which is typically used to run the query using the `find()` function.
+     *
+     * You can refine the query by chaining `RichContentQueryBuilder` functions onto the query. `RichContentQueryBuilder` functions enable you to sort, filter, and control the results `queryRichContent()` returns.
+     *
+     * `queryRichContent()` runs with these `RichContentQueryBuilder` defaults, which you can override:
      *
-     * For field support for filters and sorting, see [Supported Filters and Sorting](https://dev.wix.com/docs/rest/business-solutions/events/rich-content/filter-and-sort).
-     * To learn about working with _Query_ endpoints, see [API Query Language](https://dev.wix.com/api/rest/getting-started/api-query-language), [Sorting and Paging](https://dev.wix.com/api/rest/getting-started/pagination), and [Field Projection](https://dev.wix.com/api/rest/getting-started/field-projection).
+     * - `skip(0)`
+     * - `limit(50)`
+     * - `descending("_createdDate")`
+     * The functions that are chained to `queryRichContent()` are applied in the order they're called. For example, if you apply ascending('eventId') and then descending('id'), the results are sorted first by the event ID, and then, if there are multiple results with the same event ID, the items are sorted by ID.
      */
     (): RichContentQueryBuilder;
 }

package/type-bundles/index.bundle.d.ts

@@ -13008,15 +13008,20 @@ interface QueryRichContentsSignature {
 declare function queryRichContent$1(httpClient: HttpClient): QueryRichContentSignature;
 interface QueryRichContentSignature {
     /**
-     * Retrieves a list of rich content entities, given the provided paging, filtering, and sorting.
+     * Creates a query to retrieve a list of rich content entities.
      *
-     * Query Rich Content runs with these defaults, which you can override:
-     * - `createdDate` is sorted in `ASC` order
-     * - `paging.limit` is `100`
-     * - `paging.offset` is `0`
+     * The `queryRichContent()` function builds a query to retrieve a list of events and returns a `RichContentQueryBuilder` object.
+     *
+     * The returned object contains the query definition, which is typically used to run the query using the `find()` function.
+     *
+     * You can refine the query by chaining `RichContentQueryBuilder` functions onto the query. `RichContentQueryBuilder` functions enable you to sort, filter, and control the results `queryRichContent()` returns.
+     *
+     * `queryRichContent()` runs with these `RichContentQueryBuilder` defaults, which you can override:
      *
-     * For field support for filters and sorting, see [Supported Filters and Sorting](https://dev.wix.com/docs/rest/business-solutions/events/rich-content/filter-and-sort).
-     * To learn about working with _Query_ endpoints, see [API Query Language](https://dev.wix.com/api/rest/getting-started/api-query-language), [Sorting and Paging](https://dev.wix.com/api/rest/getting-started/pagination), and [Field Projection](https://dev.wix.com/api/rest/getting-started/field-projection).
+     * - `skip(0)`
+     * - `limit(50)`
+     * - `descending("_createdDate")`
+     * The functions that are chained to `queryRichContent()` are applied in the order they're called. For example, if you apply ascending('eventId') and then descending('id'), the results are sorted first by the event ID, and then, if there are multiple results with the same event ID, the items are sorted by ID.
      */
     (): RichContentQueryBuilder;
 }