@wix/auto_sdk_restaurants_menus 1.0.78 → 1.0.80
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/build/cjs/index.js +8 -10
- package/build/cjs/index.js.map +1 -1
- package/build/cjs/index.typings.d.ts +37 -8
- package/build/cjs/index.typings.js +1 -3
- package/build/cjs/index.typings.js.map +1 -1
- package/build/cjs/meta.d.ts +36 -3
- package/build/cjs/meta.js.map +1 -1
- package/build/cjs/schemas.js +46 -46
- package/build/cjs/schemas.js.map +1 -1
- package/build/es/index.mjs +8 -10
- package/build/es/index.mjs.map +1 -1
- package/build/es/index.typings.d.mts +37 -8
- package/build/es/index.typings.mjs +1 -3
- package/build/es/index.typings.mjs.map +1 -1
- package/build/es/meta.d.mts +36 -3
- package/build/es/meta.mjs.map +1 -1
- package/build/es/schemas.mjs +46 -46
- package/build/es/schemas.mjs.map +1 -1
- package/build/internal/cjs/index.js +8 -10
- package/build/internal/cjs/index.js.map +1 -1
- package/build/internal/cjs/index.typings.d.ts +37 -8
- package/build/internal/cjs/index.typings.js +1 -3
- package/build/internal/cjs/index.typings.js.map +1 -1
- package/build/internal/cjs/meta.d.ts +36 -3
- package/build/internal/cjs/meta.js.map +1 -1
- package/build/internal/cjs/schemas.js +46 -46
- package/build/internal/cjs/schemas.js.map +1 -1
- package/build/internal/es/index.mjs +8 -10
- package/build/internal/es/index.mjs.map +1 -1
- package/build/internal/es/index.typings.d.mts +37 -8
- package/build/internal/es/index.typings.mjs +1 -3
- package/build/internal/es/index.typings.mjs.map +1 -1
- package/build/internal/es/meta.d.mts +36 -3
- package/build/internal/es/meta.mjs.map +1 -1
- package/build/internal/es/schemas.mjs +46 -46
- package/build/internal/es/schemas.mjs.map +1 -1
- package/package.json +3 -3
|
@@ -98,6 +98,20 @@ interface Tag {
|
|
|
98
98
|
*
|
|
99
99
|
*
|
|
100
100
|
* Supported values: `title`, `meta`, `script`, `link`.
|
|
101
|
+
*
|
|
102
|
+
* Which of these an API actually accepts depends on where the tag is being set: this
|
|
103
|
+
* list is not a blanket guarantee across every API that reuses this message. Site SEO
|
|
104
|
+
* Tags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects
|
|
105
|
+
* `title`/`script`/`link` with a validation error even though they appear here —
|
|
106
|
+
* check the field description of the specific `tags`-typed field you're writing to
|
|
107
|
+
* for the types it actually supports and the error it returns.
|
|
108
|
+
*
|
|
109
|
+
* Limitation: `title` and `script` (e.g. a `script` tag with `props.type`
|
|
110
|
+
* `"application/ld+json"` carrying structured data) are supported only when
|
|
111
|
+
* `custom` is unset or `false`. Setting `custom: true` on a `title` or `script`
|
|
112
|
+
* tag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the
|
|
113
|
+
* write through the site's Advanced/Custom Tags list. To write structured data,
|
|
114
|
+
* omit `custom` (or set it to `false`).
|
|
101
115
|
*/
|
|
102
116
|
type?: string;
|
|
103
117
|
/**
|
|
@@ -110,12 +124,31 @@ interface Tag {
|
|
|
110
124
|
/** SEO tag inner content. For example, `<title> inner content </title>`. */
|
|
111
125
|
children?: string;
|
|
112
126
|
/**
|
|
113
|
-
* Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)
|
|
127
|
+
* Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) —
|
|
128
|
+
* i.e. an entry from the site's Advanced/Custom Tags list.
|
|
129
|
+
*
|
|
130
|
+
* Setting this to `true` on a write restricts which `type` values are accepted
|
|
131
|
+
* — the same restriction the Advanced/Custom Tags UI enforces. `title` and
|
|
132
|
+
* `script` tags (including JSON-LD structured data) must be sent with `custom`
|
|
133
|
+
* omitted or `false`; sending them with `custom: true` is rejected with
|
|
134
|
+
* `TAG_TYPE_NOT_ALLOWED`.
|
|
135
|
+
*
|
|
136
|
+
* Note this is a separate restriction from Site SEO Tags' own type restriction on
|
|
137
|
+
* `SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.
|
|
138
|
+
* for site-wide structured data) unconditionally. There is currently no way to set
|
|
139
|
+
* site-wide, every-page structured data through any of these APIs — write a per-page
|
|
140
|
+
* `script` tag through the Item SEO Tags API instead.
|
|
141
|
+
*
|
|
142
|
+
* This flag is scoped to that feature only. It is NOT an indicator of whether a standard tag
|
|
143
|
+
* (`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed
|
|
144
|
+
* default/pattern — standard tags always resolve with `custom: false`, even when their content comes
|
|
145
|
+
* from a page's manually saved SEO title/description override. Don't use this field to verify whether
|
|
146
|
+
* a live page reflects a manual per-page SEO edit.
|
|
114
147
|
*
|
|
115
148
|
* Limitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read
|
|
116
149
|
* only from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor
|
|
117
|
-
* or Wix Studio pages, so
|
|
118
|
-
*
|
|
150
|
+
* or Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the
|
|
151
|
+
* response entirely — there, `false` means this API could not tell, not that no custom tag exists.
|
|
119
152
|
* Pass `seoData` explicitly to resolve against a known set of tags.
|
|
120
153
|
*/
|
|
121
154
|
custom?: boolean;
|
|
@@ -1172,11 +1205,7 @@ type MenuQuery = {
|
|
|
1172
1205
|
}[];
|
|
1173
1206
|
};
|
|
1174
1207
|
declare const utils: {
|
|
1175
|
-
query:
|
|
1176
|
-
QueryBuilder: () => _wix_sdk_types.QueryBuilder<Menu, MenuQuerySpec, MenuQuery>;
|
|
1177
|
-
Filter: _wix_sdk_types.FilterFactory<Menu, MenuQuerySpec>;
|
|
1178
|
-
Sort: _wix_sdk_types.SortFactory<MenuQuerySpec>;
|
|
1179
|
-
};
|
|
1208
|
+
query: _wix_sdk_types.QueryHelpers<Menu, MenuQuerySpec, MenuQuery>;
|
|
1180
1209
|
};
|
|
1181
1210
|
/**
|
|
1182
1211
|
* > **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).
|
|
@@ -914,9 +914,7 @@ async function typedQueryMenus(query) {
|
|
|
914
914
|
}
|
|
915
915
|
}
|
|
916
916
|
var utils = {
|
|
917
|
-
query:
|
|
918
|
-
...(0, import_query_builder_utils.createQueryUtils)()
|
|
919
|
-
}
|
|
917
|
+
query: /* @__PURE__ */ (0, import_query_builder_utils.createQueryUtils)()
|
|
920
918
|
};
|
|
921
919
|
async function updateMenu2(_id, menu) {
|
|
922
920
|
const { httpClient, sideEffects } = arguments[2];
|