@wix/auto_sdk_events_forms 1.0.105 → 1.0.107

package/build/cjs/index.typings.d.ts

@@ -1423,12 +1423,19 @@ 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.
+     *
+     * 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;
@@ -2036,7 +2043,7 @@ interface Animation {
     /**
      * POINTER carries its fields directly on the union member in the JTD wall, hence
      * flat fields here (ts-proto camelCase must equal the JTD property names). A future
-     * SCROLL variant will contend for the `effect` JSON name — resolve when it lands.
+     * kind that also needs an `effect` field would contend for this JSON name.
      */
     effect?: PointerEffect;
     /** How quickly the node settles toward the pointer, in milliseconds (POINTER). */
@@ -3861,6 +3868,13 @@ interface ShapeData {
     styles?: ShapeDataStyles;
     /** Node animation. */
     animation?: Animation;
+    /** Link details for shapes that are links. */
+    link?: Link;
+    /**
+     * Alternate text describing the link's purpose for accessibility. Applies only when `link` is set.
+     * @maxLength 1000
+     */
+    altText?: string | null;
 }
 interface ShapeDataStyles {
     /**