For the last few months, we have been focusing on adding more test coverage to SaladUI.
The project has most of common components. I use it almost every day.
Give it a try and let me know if you are encountering any challenge.
For the last few months, we have been focusing on adding more test coverage to SaladUI.
The project has most of common components. I use it almost every day.
Give it a try and let me know if you are encountering any challenge.
We are actively using it. I like it. But I haven’t seen any checkins on the github repo in 3 months, so I was wondering if we are betting on the wrong horse.
Although that said, the Dung Nguyen did show up today to merge a pr, so there’s hope!
Thanks for using SaladUI, do you have any issue or suggestion?
Keep going! More components!
The core-components module is, itself, incomplete, and it would be great to make a complete replacement for it, including missing pieces such as radio buttons.
I have done a card-variant of radio buttons (select a card, any card, but only one card), but I don’t know if that’s something you would be interested in.
I think Toggle Group component Toggle Group - shadcn/ui is similar to your solution
Similar; although in my case I do need a full card ux, and the toggles are exclusive. Used in a form, as a replacement for a radio button.
Hi there, it’s a long time from last update. Today I release new version with 3 more components added:
View the story book here: SaladUI - Toggle Group
Source code on GitHub
Hi guy, I’m happy to show you some updates from SaladUI.
I’ve added a demo for using SaladUI input components in form.
https://salad-storybook.fly.dev/examples/form_demo
Breaking changes
This version introduce some change to unify interface and term for some components:
Toggle.toggle
change pressed
attribute → value
Select
change instance
→ builder
Tab.tab_trigger
change root
attribute → builder
and required exposing builder from the tabs