Debug config validate

[ameerf-wix]

Description

Related Issue

Checklist

• I have read the Contributing Guide
• I have added/updated tests for my changes (if applicable)
• I have updated documentation/rules/skills (if applicable)

Screenshots / Demos

Additional Notes

[github-actions]

Generated llms.txt preview

llms.txt

# @wix/interact

> Declarative, configuration-driven interaction library — web-native, AI-ready, and framework-agnostic.

- Install: `npm install @wix/interact @wix/motion-presets`
- Three entry points: vanilla JS (`@wix/interact`), React (`@wix/interact/react`), Web Components (`@wix/interact/web`)
- Five trigger types: hover, click, viewEnter, viewProgress, pointerMove
- Effects via named presets (`@wix/motion-presets`), keyframes, CSS transitions, or custom JS callbacks
- Configs are JSON-serializable -- designed for LLM generation

## Docs

- [Full Reference](https://wix.github.io/interact/rules/full-lean.md): Declarative configuration-driven interaction library. Binds animations to triggers via JSON config. (700 lines)
- [Integration Guide](https://wix.github.io/interact/rules/integration.md): Rules for integrating `@wix/interact` into a webpage — binding animations and effects to user-driven triggers via declarative configuration. (334 lines)
- [Validation Guide](https://wix.github.io/interact/rules/validate.md): Rules for using `@wix/interact-validate` — validate an `InteractConfig` before it reaches the runtime. (271 lines)

## Optional

- [Click Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/click.md): This document contains rules for generating click-triggered interactions in `@wix/interact`. (189 lines)
- [Hover Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/hover.md): This document contains rules for generating hover-triggered interactions in `@wix/interact`. (191 lines)
- [PointerMove Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/pointermove.md): These rules help generate pointer-driven interactions using `@wix/interact`. (279 lines)
- [ViewEnter Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/viewenter.md): This document contains rules for generating interactions that respond to elements entering the viewport using the `@wix/interact`. (226 lines)
- [ViewProgress Trigger Rules for @wix/interact](https://wix.github.io/interact/rules/viewprogress.md): These rules help generate scroll-driven interactions using `@wix/interact`. (196 lines)
- [All rules in one file](https://wix.github.io/interact/llms-full.txt): Complete concatenation (2386 lines)

llms-full.txt header

# @wix/interact v2.4.0 -- AI Rules Reference
# https://wix.github.io/interact/llms.txt
# 8 files, 2386 lines

Download full files from workflow artifacts, or run node scripts/generate-llms.mjs locally.

[ydaniv]

I think it's important we don't build that as part of the library.
It adds dependencies, and it will add bloat. We can't count on users just picking what they need and tree-shake it.
Usually users will import from CDN, or just import the library as-is.
And also tools that check the build size will show a much larger size which reflects bad visually.

[ydaniv]

pageVisible, besides being Wix-only, is a wrapper above viewEnter + triggerType: 'state', which is now on the effect. It's becoming somewhat problematic to keep.

[ameerf-wix]

oh I missed it because it is not really documented anywhere that it must have triggerType: 'state' - I guess that it is another strong indication to remove it. Maybe we can also make sure that wix do the transformation from pageVisible to viewEnter + triggerType: 'state' and pass a valid config to Interact

[ydaniv]

What are we comparing here? Length of string? Or do these strings represent numbers?

[ameerf-wix]

I think it is lexical order on strings that represent paths in the config - does not seem ideal, should fix that