-
Notifications
You must be signed in to change notification settings - Fork 144
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
New Design for Vue 3 JSX #10
Comments
About '.sync' modifierIn vue-next, we should use <MyComp v-model={[value, "foo"]} /> But I think this is not suitable for TSX in some points.
I guess it is not impossible to solve them by changing type definitions, but it will makes type definitions too complex. Simple solution is giving up v-model. <MyComp foo={value} on={{ "update:foo": v => value = v }} /> Is there any other (more smart) solutions ? |
<MyComp foo={value} on={{ "update:foo": v => value = v }} /> Will you change type definitions when giving up v-model like above. interface Props {
foo?: string;
on?: {
'update:foo': (val: string) => void;
}
} Or interface Props {
vModel?: [string, 'foo']
} But I think it will be a misunderstand because |
Implementation Detail and new Design to discuss
The text was updated successfully, but these errors were encountered: