@wix/auto_sdk_restaurants_menus 1.0.78 → 1.0.80

package/build/internal/es/index.typings.d.mts

@@ -115,6 +115,20 @@ interface Tag {
      *
      *
      * Supported values: `title`, `meta`, `script`, `link`.
+     *
+     * Which of these an API actually accepts depends on where the tag is being set: this
+     * list is not a blanket guarantee across every API that reuses this message. Site SEO
+     * Tags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects
+     * `title`/`script`/`link` with a validation error even though they appear here —
+     * check the field description of the specific `tags`-typed field you're writing to
+     * for the types it actually supports and the error it returns.
+     *
+     * Limitation: `title` and `script` (e.g. a `script` tag with `props.type`
+     * `"application/ld+json"` carrying structured data) are supported only when
+     * `custom` is unset or `false`. Setting `custom: true` on a `title` or `script`
+     * tag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the
+     * write through the site's Advanced/Custom Tags list. To write structured data,
+     * omit `custom` (or set it to `false`).
      */
     type?: string;
     /**
@@ -127,12 +141,31 @@ interface Tag {
     /** SEO tag inner content. For example, `<title> inner content </title>`. */
     children?: string;
     /**
-     * Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).
+     * Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) —
+     * i.e. an entry from the site's Advanced/Custom Tags list.
+     *
+     * Setting this to `true` on a write restricts which `type` values are accepted
+     * — the same restriction the Advanced/Custom Tags UI enforces. `title` and
+     * `script` tags (including JSON-LD structured data) must be sent with `custom`
+     * omitted or `false`; sending them with `custom: true` is rejected with
+     * `TAG_TYPE_NOT_ALLOWED`.
+     *
+     * Note this is a separate restriction from Site SEO Tags' own type restriction on
+     * `SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.
+     * for site-wide structured data) unconditionally. There is currently no way to set
+     * site-wide, every-page structured data through any of these APIs — write a per-page
+     * `script` tag through the Item SEO Tags API instead.
+     *
+     * This flag is scoped to that feature only. It is NOT an indicator of whether a standard tag
+     * (`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed
+     * default/pattern — standard tags always resolve with `custom: false`, even when their content comes
+     * from a page's manually saved SEO title/description override. Don't use this field to verify whether
+     * a live page reflects a manual per-page SEO edit.
      *
      * Limitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read
      * only from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor
-     * or Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For
-     * those pages `false` therefore does not mean "not a custom tag" — it means this API could not tell.
+     * or Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the
+     * response entirely — there, `false` means this API could not tell, not that no custom tag exists.
      * Pass `seoData` explicitly to resolve against a known set of tags.
      */
     custom?: boolean;
@@ -1222,11 +1255,7 @@ type MenuQuery = {
     }[];
 };
 declare const utils: {
-    query: {
-        QueryBuilder: () => _wix_sdk_types.QueryBuilder<Menu, MenuQuerySpec, MenuQuery>;
-        Filter: _wix_sdk_types.FilterFactory<Menu, MenuQuerySpec>;
-        Sort: _wix_sdk_types.SortFactory<MenuQuerySpec>;
-    };
+    query: _wix_sdk_types.QueryHelpers<Menu, MenuQuerySpec, MenuQuery>;
 };
 /**
  * > **Note:** The Menu API only works with the Wix Restaurants Menus app. Make sure you have installed this app from the [Wix App Market](https://www.wix.com/app-market/wix-restaurants-menus-new).

package/build/internal/es/index.typings.mjs

@@ -876,9 +876,7 @@ async function typedQueryMenus(query) {
   }
 }
 var utils = {
-  query: {
-    ...createQueryUtils()
-  }
+  query: /* @__PURE__ */ createQueryUtils()
 };
 async function updateMenu2(_id, menu) {
   const { httpClient, sideEffects } = arguments[2];