@shopkit/data-layer 1.5.0 → 1.6.0
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.
- package/dist/adapters/index.js +26 -0
- package/dist/adapters/index.js.map +1 -1
- package/dist/adapters/index.mjs +26 -0
- package/dist/adapters/index.mjs.map +1 -1
- package/dist/index.js +26 -0
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +26 -0
- package/dist/index.mjs.map +1 -1
- package/dist/models/index.d.mts +11 -0
- package/dist/models/index.d.ts +11 -0
- package/package.json +1 -1
package/dist/models/index.d.mts
CHANGED
|
@@ -461,6 +461,17 @@ interface IQueryCollectionsRequest {
|
|
|
461
461
|
* detected here. On a product template the widget comes back empty.
|
|
462
462
|
*/
|
|
463
463
|
useRouteHandle?: boolean;
|
|
464
|
+
/**
|
|
465
|
+
* Collections to fetch, by handle, in this order. Becomes
|
|
466
|
+
* `filter.handle: { $in: handles }` unless the filter already names a handle,
|
|
467
|
+
* and collections come back in this order when no `sort` is given.
|
|
468
|
+
*
|
|
469
|
+
* The visual editor's collection picker writes this key (as it does for
|
|
470
|
+
* `COLLECTION_BY_HANDLES`), so a data source declared with `handles` stays
|
|
471
|
+
* editable by the merchant; one declared with `filter.handle` is fixed.
|
|
472
|
+
* An empty list fetches nothing (`data: []`) rather than every collection.
|
|
473
|
+
*/
|
|
474
|
+
handles?: string[];
|
|
464
475
|
}
|
|
465
476
|
/**
|
|
466
477
|
* Why a queryCollections call failed, in `error.code`.
|
package/dist/models/index.d.ts
CHANGED
|
@@ -461,6 +461,17 @@ interface IQueryCollectionsRequest {
|
|
|
461
461
|
* detected here. On a product template the widget comes back empty.
|
|
462
462
|
*/
|
|
463
463
|
useRouteHandle?: boolean;
|
|
464
|
+
/**
|
|
465
|
+
* Collections to fetch, by handle, in this order. Becomes
|
|
466
|
+
* `filter.handle: { $in: handles }` unless the filter already names a handle,
|
|
467
|
+
* and collections come back in this order when no `sort` is given.
|
|
468
|
+
*
|
|
469
|
+
* The visual editor's collection picker writes this key (as it does for
|
|
470
|
+
* `COLLECTION_BY_HANDLES`), so a data source declared with `handles` stays
|
|
471
|
+
* editable by the merchant; one declared with `filter.handle` is fixed.
|
|
472
|
+
* An empty list fetches nothing (`data: []`) rather than every collection.
|
|
473
|
+
*/
|
|
474
|
+
handles?: string[];
|
|
464
475
|
}
|
|
465
476
|
/**
|
|
466
477
|
* Why a queryCollections call failed, in `error.code`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@shopkit/data-layer",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.6.0",
|
|
4
4
|
"description": "Enterprise data abstraction layer providing unified API for e-commerce platforms including Shopify and custom backends",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"module": "dist/index.mjs",
|