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 Radio page disappeared once RadioGroup got released.

Good idea! I guess we could do like on #881 and make the label size configurable, by taking into account this fix #894.

Good idea! I guess we could do like on #881 and make the label size configurable, by taking into account this fix #894.

True, I did miss to change checkbox in ui.config.ts to make this work

I'm unable to push on this PR to fix the conflicts. 🤔

! [remote rejected] HEAD -> dev (refusing to allow a GitHub App to create or update workflow .github/workflows/ci-dev.yml without workflows permission)

I'm unable to push on this PR to fix the conflicts. 🤔

! [remote rejected] HEAD -> dev (refusing to allow a GitHub App to create or update workflow .github/workflows/ci-dev.yml without workflows permission)

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 CheckboxGroup component whereas the RadioGroup has some logic tied to it. This one would be just a shortcut for a v-for and therefore a bit overkill in my opinion.

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 CheckboxGroup component whereas the RadioGroup has some logic tied to it. This one would be just a shortcut for a v-for and therefore a bit overkill in my opinion.

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.