@viu/emporix-sdk 2.28.0 → 2.28.2

package/dist/index.cjs

@@ -890,7 +890,7 @@ var HttpClient = class {
 };
 
 // package.json
-var version = "2.28.0";
+var version = "2.28.2";
 
 // src/version.ts
 var SDK_VERSION = version;
@@ -1320,9 +1320,28 @@ var ProductService = class {
    * so a bare term (e.g. "in time") 400s with "No value for key …". This builds
    * a `name:(~<term>)` regex filter (regex metacharacters escaped) and delegates
    * to {@link search}.
+   *
+   * Safe for text a shopper typed: `( ) "` are **removed** rather than escaped,
+   * because Emporix parses the filter's own structure before it looks at the
+   * regex. `name:(~a \()` is rejected with «Missing closing parenthesis in value»
+   * even though the paren is escaped, so a search box would 400 on an opening
+   * bracket. Measured against a live tenant on 2026-08-03: of every regex
+   * metacharacter only those three break; the rest survive escaping.
+   *
+   * A query consisting solely of those characters leaves nothing to search for and
+   * returns an empty page without a request — `name:(~)` is a 400.
    */
   async searchByName(query, params = {}, auth2 = ANON) {
-    const escaped = query.trim().replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
+    const term = query.replace(/[()"]/g, " ").replace(/\s+/g, " ").trim();
+    if (term === "") {
+      return {
+        items: [],
+        pageNumber: params.pageNumber ?? 1,
+        pageSize: params.pageSize ?? 50,
+        hasNextPage: false
+      };
+    }
+    const escaped = term.replace(/[.*+?^${}|[\]\\]/g, "\\$&");
     return this.search(`name:(~${escaped})`, params, auth2);
   }
   /**
@@ -1662,8 +1681,22 @@ var CategoryService = class {
   }
   /**
    * The catalogue's **root categories** — the published category trees
-   * (`GET /category-trees`). Use these for top-level storefront navigation;
-   * drill into a node's children with {@link subcategories}.
+   * (`GET /category-trees`).
+   *
+   * Returns `CategoryNode[]` (the generated `CategoryTree`), not `Category[]`.
+   * The two differ: `Category` carries `parentId` and no `subcategories`,
+   * `CategoryTree` the reverse, and this endpoint answers with the latter.
+   * Measured against a live tenant on 2026-08-04 — every node had
+   * `subcategories` or nothing, none had `parentId`.
+   *
+   * **Children arrive inline in `subcategories`.** Do not reach for
+   * {@link subcategories} to drill down: that method reads category-to-category
+   * *assignments* (`/categories/{id}/assignments`, filtered to
+   * `ref.type === "CATEGORY"`), which is a different feature — on the tenant this
+   * was measured on, that filter answered empty for every category while the
+   * `"PRODUCT"` filter behind {@link productsIn} worked fine.
+   * {@link childCategories} hits `/categories/{id}/subcategories` and answers
+   * **404** for a tree root. One call gives you the whole hierarchy.
    */
   async tree(auth2 = ANON2) {
     return this.ctx.http.request({