-
Notifications
You must be signed in to change notification settings - Fork 88
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
[next] fix: unify modelValue
naming
#4990
Conversation
9ee6504
to
eac4c2e
Compare
modelValue
naming
eac4c2e
to
4602c34
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, modelValue
should be used only in a meaning of a model, controlled value of the component, not a name for value
.
Then it would align with Vue's model (input[type=checkbox]
has v-model
for checked
, not value
) and meaning of v-model
directive (there always would be update:modelValue
for updating component's model).
@ShGKme Thanks for the insight. I didn't look at it this way yet, but I think it makes sense. I will adjust the PR accordingly. |
Signed-off-by: Raimund Schlüßler <[email protected]>
4602c34
to
6514aa3
Compare
I adjusted the PR. It now only contains changes related to renaming |
☑️ Resolves
value / modelValue
. Everyvalue
prop got renamed tomodelValue
to align with the new usage by vue 3. For some components we did this already, so here I migrated the rest to have it consistent.