[Feature Request] [Enhancement] v-radio without using v-radio-group
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 41k
- Forks
- 7.1k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 11
Description
Problem to solve
I would like to be able to use v-radio components without having to wrap them inside a v-radio-group.
This would be especially useful when displaying radio buttons inside a table.
I saw the related issue from 2018, but it didn’t lead to a good solution.
Proposed solution
Ideally,
the v-model of a v-radio would return the associated value when the radio is checked;
and it would return null when it is not.
This would also allow us to use the checked state for styling purposes.
Right now, if two radio buttons share the same name attribute, selecting one does not visually uncheck the other, which causes a display issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how v-radio and v-radio-group currently handle v-model, checked state, and shared name attributes, then read the related issue from 2018 for prior constraints. Done means standalone v-radio components return their associated value when checked, return null otherwise, and visually reflect the checked state when sharing a name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100