-
Notifications
You must be signed in to change notification settings - Fork 85
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
chore: prepare v8.20.0 release #6175
base: master
Are you sure you want to change the base?
Conversation
Using of
as it emits 'update:value',
Should we consider it a breaking change? |
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.
@Antreesy Yes it's a breaking change IMO.
I wouldn't call it a breaking change. This is invalid usage, component didn't have documented |
I have to check, if
Waiting for you then |
Also would consider this unexpected / undocumented / invalid behavior. |
|
Tested.
|
134b3b3
to
f672168
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.
Would also add the note @ShGKme proposed.
Signed-off-by: Maksim Sukharev <[email protected]>
f672168
to
8660dad
Compare
Has been merged: On review: |
v8.20.0 (2024-10-29)
Full Changelog
📝 Notes
Now you can use
v-model
directive,:model-value
prop, and@update:model-value
(@update:modelValue
) event in all data input components to have compatibility with v9 in the future.If you already use
v-model
with a custom writable computed on:value.sync
components before, it might not work as expected anymore. Make sure to remove or adjust it before update.See the full list in v9 breaking changes.
🚀 Enhancements
v-model
support for input-like components #5418 (kyteinsky)v-model
props/events #6172 (ShGKme)🐛 Fixed bugs
Changed