-
Notifications
You must be signed in to change notification settings - Fork 573
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
feat(CheckboxGroup): new component #895
Conversation
The latest updates on your projects. Learn more about Vercel for Git βοΈ
|
I'm not fully sure how to update the docs, so I'm happy to get directions. But I marked this as ready to merge anyway, since it could need something else done that I'm not aware of. Also, I've noticed that the |
I'm unable to push on this PR to fix the conflicts. π€
|
I do remember noticing a failed run (due to not having permissions) as soon as I forked the repo UPDATE: but now if I want to check what could be causing it I do correctly see that workflows are disabled on my side |
Sorry but I won't be merging this, I've thought about it and it doesn't really make that much sense to have a |
No problem. As I said in the PR description this was only for streamlining naming convention and developer experience at a conceptual level, thus not required. |
π Linked issue
I decided not to create an issue for such little task
β Type of change
π Description
Much like the new
RadioGroup
component it could be useful (both as a standard as well as a dev experience) to have a similar component for Checkboxes.π Checklist