@wix/auto_sdk_table-reservations_experiences 1.0.51 → 1.0.53

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.
Files changed (37) hide show
  1. package/build/cjs/index.d.ts +2 -2
  2. package/build/cjs/index.js.map +1 -1
  3. package/build/cjs/index.typings.d.ts +2 -2
  4. package/build/cjs/index.typings.js.map +1 -1
  5. package/build/cjs/meta.d.ts +25 -3
  6. package/build/cjs/meta.js.map +1 -1
  7. package/build/cjs/schemas.js +10 -10
  8. package/build/cjs/schemas.js.map +1 -1
  9. package/build/cjs/{table-reservations-v1-experience-experiences.universal-DmJvCcqC.d.ts → table-reservations-v1-experience-experiences.universal-CQEGusXL.d.ts} +25 -6
  10. package/build/es/index.d.mts +2 -2
  11. package/build/es/index.mjs.map +1 -1
  12. package/build/es/index.typings.d.mts +2 -2
  13. package/build/es/index.typings.mjs.map +1 -1
  14. package/build/es/meta.d.mts +25 -3
  15. package/build/es/meta.mjs.map +1 -1
  16. package/build/es/schemas.mjs +10 -10
  17. package/build/es/schemas.mjs.map +1 -1
  18. package/build/es/{table-reservations-v1-experience-experiences.universal-DmJvCcqC.d.mts → table-reservations-v1-experience-experiences.universal-CQEGusXL.d.mts} +25 -6
  19. package/build/internal/cjs/index.d.ts +2 -2
  20. package/build/internal/cjs/index.js.map +1 -1
  21. package/build/internal/cjs/index.typings.d.ts +2 -2
  22. package/build/internal/cjs/index.typings.js.map +1 -1
  23. package/build/internal/cjs/meta.d.ts +25 -3
  24. package/build/internal/cjs/meta.js.map +1 -1
  25. package/build/internal/cjs/schemas.js +10 -10
  26. package/build/internal/cjs/schemas.js.map +1 -1
  27. package/build/internal/cjs/{table-reservations-v1-experience-experiences.universal-JFfnG_cQ.d.ts → table-reservations-v1-experience-experiences.universal-CK8DH5zA.d.ts} +25 -6
  28. package/build/internal/es/index.d.mts +2 -2
  29. package/build/internal/es/index.mjs.map +1 -1
  30. package/build/internal/es/index.typings.d.mts +2 -2
  31. package/build/internal/es/index.typings.mjs.map +1 -1
  32. package/build/internal/es/meta.d.mts +25 -3
  33. package/build/internal/es/meta.mjs.map +1 -1
  34. package/build/internal/es/schemas.mjs +10 -10
  35. package/build/internal/es/schemas.mjs.map +1 -1
  36. package/build/internal/es/{table-reservations-v1-experience-experiences.universal-JFfnG_cQ.d.mts → table-reservations-v1-experience-experiences.universal-CK8DH5zA.d.mts} +25 -6
  37. package/package.json +2 -2
@@ -237,7 +237,7 @@ var CreateExperienceRequest = z.object({
237
237
  "SEO tag inner content. For example, `<title> inner content </title>`."
238
238
  ).optional(),
239
239
  custom: z.boolean().describe(
240
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
240
+ "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."
241
241
  ).optional(),
242
242
  disabled: z.boolean().describe(
243
243
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -500,7 +500,7 @@ var CreateExperienceResponse = z.object({
500
500
  "SEO tag inner content. For example, `<title> inner content </title>`."
501
501
  ).optional(),
502
502
  custom: z.boolean().describe(
503
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
503
+ "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."
504
504
  ).optional(),
505
505
  disabled: z.boolean().describe(
506
506
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -768,7 +768,7 @@ var GetExperienceResponse = z.object({
768
768
  "SEO tag inner content. For example, `<title> inner content </title>`."
769
769
  ).optional(),
770
770
  custom: z.boolean().describe(
771
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
771
+ "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."
772
772
  ).optional(),
773
773
  disabled: z.boolean().describe(
774
774
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1040,7 +1040,7 @@ var GetExperienceBySlugResponse = z.object({
1040
1040
  "SEO tag inner content. For example, `<title> inner content </title>`."
1041
1041
  ).optional(),
1042
1042
  custom: z.boolean().describe(
1043
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
1043
+ "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."
1044
1044
  ).optional(),
1045
1045
  disabled: z.boolean().describe(
1046
1046
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1312,7 +1312,7 @@ var UpdateExperienceRequest = z.object({
1312
1312
  "SEO tag inner content. For example, `<title> inner content </title>`."
1313
1313
  ).optional(),
1314
1314
  custom: z.boolean().describe(
1315
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
1315
+ "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."
1316
1316
  ).optional(),
1317
1317
  disabled: z.boolean().describe(
1318
1318
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1575,7 +1575,7 @@ var UpdateExperienceResponse = z.object({
1575
1575
  "SEO tag inner content. For example, `<title> inner content </title>`."
1576
1576
  ).optional(),
1577
1577
  custom: z.boolean().describe(
1578
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
1578
+ "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."
1579
1579
  ).optional(),
1580
1580
  disabled: z.boolean().describe(
1581
1581
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1873,7 +1873,7 @@ var QueryExperiencesResponse = z.object({
1873
1873
  "SEO tag inner content. For example, `<title> inner content </title>`."
1874
1874
  ).optional(),
1875
1875
  custom: z.boolean().describe(
1876
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
1876
+ "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."
1877
1877
  ).optional(),
1878
1878
  disabled: z.boolean().describe(
1879
1879
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -2444,7 +2444,7 @@ var SearchExperiencesResponse = z.object({
2444
2444
  "SEO tag inner content. For example, `<title> inner content </title>`."
2445
2445
  ).optional(),
2446
2446
  custom: z.boolean().describe(
2447
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
2447
+ "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."
2448
2448
  ).optional(),
2449
2449
  disabled: z.boolean().describe(
2450
2450
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -2993,7 +2993,7 @@ var BulkUpdateExperiencesRequest = z.object({
2993
2993
  "SEO tag inner content. For example, `<title> inner content </title>`."
2994
2994
  ).optional(),
2995
2995
  custom: z.boolean().describe(
2996
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
2996
+ "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."
2997
2997
  ).optional(),
2998
2998
  disabled: z.boolean().describe(
2999
2999
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -3297,7 +3297,7 @@ var BulkUpdateExperiencesResponse = z.object({
3297
3297
  "SEO tag inner content. For example, `<title> inner content </title>`."
3298
3298
  ).optional(),
3299
3299
  custom: z.boolean().describe(
3300
- "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages)."
3300
+ "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."
3301
3301
  ).optional(),
3302
3302
  disabled: z.boolean().describe(
3303
3303
  "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."