feat: add v-model support for input-like components#5418
Conversation
ShGKme
left a comment
There was a problem hiding this comment.
I think, that would be good to add model to every component that has modelValue in the next version.
Just to make further migration to v9 easier for library users.
All these components from the Breaking Changes list where it doesn't conflict with the current implementation.
https://github.com/nextcloud-libraries/nextcloud-vue/blob/next/CHANGELOG.md
|
Hey @kyteinsky! What do you think about adding |
|
Hello @ShGKme , sorry I didn't find time for it recently. Yeah, looks like a sound reasoning. Is it alright if I do that the next week? |
Sure |
1e5f927 to
eb74cc9
Compare
|
Some components did not need modification and already work with v-model:
|
Confirm, all of them have the default model with
It is the same as |
This facilitates migration from Vue 2 to Vue Next (3) easier. Also comes with the v-model advantages like the number modifier (v-model.number) which is not possible with .sync prop modifier. Signed-off-by: Anupam Kumar <kyteinsky@gmail.com>
Signed-off-by: Maksim Sukharev <antreesy.web@gmail.com>
Signed-off-by: Maksim Sukharev <antreesy.web@gmail.com>
eb74cc9 to
19e41ed
Compare
Added model for NcActionRadio Added docs examples with v-model for all components from Breaking changes list:
|
checkedSigned-off-by: Maksim Sukharev <antreesy.web@gmail.com>
19e41ed to
bdb0677
Compare
|
/backport 4e6ba04 to next |
Can we get this in nc/vue 8.x or does it not matter since it was added in vue9 recently (#4994)? Would be a nice QOL improvement still.
π Checklist
nextrequested with a Vue 3 upgrade