-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bindings for Zag.js (headless UI toolkit) & usage examples #529
Comments
Maybe @segunadebayo @anubra266 @cschroeter can guide us to see what we need to do and integrate it if necessary or show directly the example with Zag.js |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be very useful to be able to use a UI toolkit for common abstractions like tooltips, dialogs, accordions, toggles etc. Personally I like the headless approach taken by libraries in the React world like
react-aria
andradix
, but those are React-specific.The people at Chakra UI made a pretty cool set of libraries, Zag.js (and its companion library, Ark UI, for framework-specific headless components).
In theory these should be usable with Brisa, because they are not dependent on any one specific framework; but in practice it looks like it would be useful to have some level of integration into this, for instance the
useMachine
andnormalizeProps
helpers that are present forreact
/solid
/vue
are unclear how you would achieve the same logic with Brisa (e.g. see the examples in their Tooltip state machine, you can change the framework for different framework examples in the top left corner).They have an example of how you would do things with Lit, as well as Vanilla TS, so it's definitely possible but not super easy without some kind of interop layer.
If something like this were present then Brisa would immediately have a robust headless UI library to work with, which would be sweet.
The text was updated successfully, but these errors were encountered: