@wix/auto_sdk_events_forms 1.0.108 → 1.0.109

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.
@@ -1591,6 +1591,13 @@ interface Tag {
1591
1591
  *
1592
1592
  *
1593
1593
  * Supported values: `title`, `meta`, `script`, `link`.
1594
+ *
1595
+ * Which of these an API actually accepts depends on where the tag is being set: this
1596
+ * list is not a blanket guarantee across every API that reuses this message. Site SEO
1597
+ * Tags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects
1598
+ * `title`/`script`/`link` with a validation error even though they appear here —
1599
+ * check the field description of the specific `tags`-typed field you're writing to
1600
+ * for the types it actually supports and the error it returns.
1594
1601
  */
1595
1602
  type?: string;
1596
1603
  /**
@@ -1606,6 +1613,12 @@ interface Tag {
1606
1613
  * Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) —
1607
1614
  * i.e. an entry from the site's Advanced/Custom Tags list.
1608
1615
  *
1616
+ * Note this is a separate restriction from Site SEO Tags' own type restriction on
1617
+ * `SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.
1618
+ * for site-wide structured data) unconditionally. There is currently no way to set
1619
+ * site-wide, every-page structured data through any of these APIs — write a per-page
1620
+ * `script` tag through the Item SEO Tags API instead.
1621
+ *
1609
1622
  * This flag is scoped to that feature only. It is NOT an indicator of whether a standard tag
1610
1623
  * (`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed
1611
1624
  * default/pattern — standard tags always resolve with `custom: false`, even when their content comes