@wix/auto_sdk_online-programs_programs 1.0.23 → 1.0.25
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.d.ts +2 -2
- package/build/cjs/index.js.map +1 -1
- package/build/cjs/index.typings.d.ts +2 -2
- package/build/cjs/index.typings.js.map +1 -1
- package/build/cjs/meta.d.ts +17 -2
- package/build/cjs/meta.js.map +1 -1
- package/build/cjs/{online-programs-v3-program-programs.universal-BT1XB9EK.d.ts → online-programs-v3-program-programs.universal-BkiNXEkh.d.ts} +20 -6
- package/build/cjs/schemas.js +14 -14
- package/build/cjs/schemas.js.map +1 -1
- package/build/es/index.d.mts +2 -2
- package/build/es/index.mjs.map +1 -1
- package/build/es/index.typings.d.mts +2 -2
- package/build/es/index.typings.mjs.map +1 -1
- package/build/es/meta.d.mts +17 -2
- package/build/es/meta.mjs.map +1 -1
- package/build/es/{online-programs-v3-program-programs.universal-BT1XB9EK.d.mts → online-programs-v3-program-programs.universal-BkiNXEkh.d.mts} +20 -6
- package/build/es/schemas.mjs +14 -14
- package/build/es/schemas.mjs.map +1 -1
- package/build/internal/cjs/index.d.ts +2 -2
- package/build/internal/cjs/index.js.map +1 -1
- package/build/internal/cjs/index.typings.d.ts +2 -2
- package/build/internal/cjs/index.typings.js.map +1 -1
- package/build/internal/cjs/meta.d.ts +17 -2
- package/build/internal/cjs/meta.js.map +1 -1
- package/build/internal/cjs/{online-programs-v3-program-programs.universal-CY1iRKeB.d.ts → online-programs-v3-program-programs.universal-D5nSylw5.d.ts} +20 -6
- package/build/internal/cjs/schemas.js +14 -14
- package/build/internal/cjs/schemas.js.map +1 -1
- package/build/internal/es/index.d.mts +2 -2
- package/build/internal/es/index.mjs.map +1 -1
- package/build/internal/es/index.typings.d.mts +2 -2
- package/build/internal/es/index.typings.mjs.map +1 -1
- package/build/internal/es/meta.d.mts +17 -2
- package/build/internal/es/meta.mjs.map +1 -1
- package/build/internal/es/{online-programs-v3-program-programs.universal-CY1iRKeB.d.mts → online-programs-v3-program-programs.universal-D5nSylw5.d.mts} +20 -6
- package/build/internal/es/schemas.mjs +14 -14
- package/build/internal/es/schemas.mjs.map +1 -1
- package/package.json +2 -2
|
@@ -324,7 +324,22 @@ interface Tag {
|
|
|
324
324
|
meta?: Record<string, any> | null;
|
|
325
325
|
/** SEO tag inner content. For example, `<title> inner content </title>`. */
|
|
326
326
|
children?: string;
|
|
327
|
-
/**
|
|
327
|
+
/**
|
|
328
|
+
* Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) —
|
|
329
|
+
* i.e. an entry from the site's Advanced/Custom Tags list.
|
|
330
|
+
*
|
|
331
|
+
* This flag is scoped to that feature only. It is NOT an indicator of whether a standard tag
|
|
332
|
+
* (`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed
|
|
333
|
+
* default/pattern — standard tags always resolve with `custom: false`, even when their content comes
|
|
334
|
+
* from a page's manually saved SEO title/description override. Don't use this field to verify whether
|
|
335
|
+
* a live page reflects a manual per-page SEO edit.
|
|
336
|
+
*
|
|
337
|
+
* Limitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read
|
|
338
|
+
* only from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor
|
|
339
|
+
* or Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the
|
|
340
|
+
* response entirely — there, `false` means this API could not tell, not that no custom tag exists.
|
|
341
|
+
* Pass `seoData` explicitly to resolve against a known set of tags.
|
|
342
|
+
*/
|
|
328
343
|
custom?: boolean;
|
|
329
344
|
/** Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines. */
|
|
330
345
|
disabled?: boolean;
|
|
@@ -2980,15 +2995,14 @@ declare const utils: {
|
|
|
2980
2995
|
query: {
|
|
2981
2996
|
QueryBuilder: () => _wix_sdk_types.QueryBuilder<Program, ProgramQuerySpec, ProgramQuery>;
|
|
2982
2997
|
Filter: _wix_sdk_types.FilterFactory<Program, ProgramQuerySpec>;
|
|
2983
|
-
Sort: _wix_sdk_types.SortFactory<ProgramQuerySpec>;
|
|
2998
|
+
Sort: _wix_sdk_types.SortFactory<ProgramQuerySpec>; /**
|
|
2999
|
+
* List of nested aggregations.
|
|
3000
|
+
* @maxSize 1000
|
|
3001
|
+
*/
|
|
2984
3002
|
};
|
|
2985
3003
|
search: {
|
|
2986
3004
|
SearchBuilder: () => _wix_sdk_types.SearchBuilder<Program, ProgramSearchSpec, ProgramSearch>;
|
|
2987
3005
|
Filter: _wix_sdk_types.FilterFactory<Program, ProgramSearchSpec>;
|
|
2988
|
-
/**
|
|
2989
|
-
* Field to aggregate by, matches the one provided in request.
|
|
2990
|
-
* @maxLength 200
|
|
2991
|
-
*/
|
|
2992
3006
|
Sort: _wix_sdk_types.SortFactory<ProgramSearchSpec>;
|
|
2993
3007
|
SearchParams: _wix_sdk_types.SearchParamsFactory<ProgramSearchSpec>;
|
|
2994
3008
|
Aggregation: _wix_sdk_types.AggregationFactory<ProgramSearchSpec>;
|
|
@@ -80,7 +80,7 @@ var CreateProgramRequest = z.object({
|
|
|
80
80
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
81
81
|
).optional(),
|
|
82
82
|
custom: z.boolean().describe(
|
|
83
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
83
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
84
84
|
).optional(),
|
|
85
85
|
disabled: z.boolean().describe(
|
|
86
86
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -244,7 +244,7 @@ var CreateProgramResponse = z.object({
|
|
|
244
244
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
245
245
|
).optional(),
|
|
246
246
|
custom: z.boolean().describe(
|
|
247
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
247
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
248
248
|
).optional(),
|
|
249
249
|
disabled: z.boolean().describe(
|
|
250
250
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -407,7 +407,7 @@ var DuplicateProgramResponse = z.object({
|
|
|
407
407
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
408
408
|
).optional(),
|
|
409
409
|
custom: z.boolean().describe(
|
|
410
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
410
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
411
411
|
).optional(),
|
|
412
412
|
disabled: z.boolean().describe(
|
|
413
413
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -577,7 +577,7 @@ var GetProgramResponse = z.object({
|
|
|
577
577
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
578
578
|
).optional(),
|
|
579
579
|
custom: z.boolean().describe(
|
|
580
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
580
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
581
581
|
).optional(),
|
|
582
582
|
disabled: z.boolean().describe(
|
|
583
583
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -738,7 +738,7 @@ var UpdateProgramRequest = z.object({
|
|
|
738
738
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
739
739
|
).optional(),
|
|
740
740
|
custom: z.boolean().describe(
|
|
741
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
741
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
742
742
|
).optional(),
|
|
743
743
|
disabled: z.boolean().describe(
|
|
744
744
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -902,7 +902,7 @@ var UpdateProgramResponse = z.object({
|
|
|
902
902
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
903
903
|
).optional(),
|
|
904
904
|
custom: z.boolean().describe(
|
|
905
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
905
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
906
906
|
).optional(),
|
|
907
907
|
disabled: z.boolean().describe(
|
|
908
908
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -1106,7 +1106,7 @@ var QueryProgramsResponse = z.object({
|
|
|
1106
1106
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
1107
1107
|
).optional(),
|
|
1108
1108
|
custom: z.boolean().describe(
|
|
1109
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
1109
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
1110
1110
|
).optional(),
|
|
1111
1111
|
disabled: z.boolean().describe(
|
|
1112
1112
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -1600,7 +1600,7 @@ var SearchProgramsResponse = z.object({
|
|
|
1600
1600
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
1601
1601
|
).optional(),
|
|
1602
1602
|
custom: z.boolean().describe(
|
|
1603
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
1603
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
1604
1604
|
).optional(),
|
|
1605
1605
|
disabled: z.boolean().describe(
|
|
1606
1606
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2035,7 +2035,7 @@ var PublishProgramResponse = z.object({
|
|
|
2035
2035
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2036
2036
|
).optional(),
|
|
2037
2037
|
custom: z.boolean().describe(
|
|
2038
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
2038
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2039
2039
|
).optional(),
|
|
2040
2040
|
disabled: z.boolean().describe(
|
|
2041
2041
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2209,7 +2209,7 @@ var EndProgramResponse = z.object({
|
|
|
2209
2209
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2210
2210
|
).optional(),
|
|
2211
2211
|
custom: z.boolean().describe(
|
|
2212
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
2212
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2213
2213
|
).optional(),
|
|
2214
2214
|
disabled: z.boolean().describe(
|
|
2215
2215
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2383,7 +2383,7 @@ var ArchiveProgramResponse = z.object({
|
|
|
2383
2383
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2384
2384
|
).optional(),
|
|
2385
2385
|
custom: z.boolean().describe(
|
|
2386
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
2386
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2387
2387
|
).optional(),
|
|
2388
2388
|
disabled: z.boolean().describe(
|
|
2389
2389
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2559,7 +2559,7 @@ var BulkUpdateProgramsRequest = z.object({
|
|
|
2559
2559
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2560
2560
|
).optional(),
|
|
2561
2561
|
custom: z.boolean().describe(
|
|
2562
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
2562
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2563
2563
|
).optional(),
|
|
2564
2564
|
disabled: z.boolean().describe(
|
|
2565
2565
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2763,7 +2763,7 @@ var BulkUpdateProgramsResponse = z.object({
|
|
|
2763
2763
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2764
2764
|
).optional(),
|
|
2765
2765
|
custom: z.boolean().describe(
|
|
2766
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
2766
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2767
2767
|
).optional(),
|
|
2768
2768
|
disabled: z.boolean().describe(
|
|
2769
2769
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2965,7 +2965,7 @@ var ListSampleProgramsResponse = z.object({
|
|
|
2965
2965
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2966
2966
|
).optional(),
|
|
2967
2967
|
custom: z.boolean().describe(
|
|
2968
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
|
|
2968
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2969
2969
|
).optional(),
|
|
2970
2970
|
disabled: z.boolean().describe(
|
|
2971
2971
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|