-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
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
Static type="checkbox" with v-bind (fix #7811) #7819
Conversation
@@ -34,7 +34,7 @@ function preTransformNode (el: ASTElement, options: CompilerOptions) { | |||
if (map[':type'] || map['v-bind:type']) { | |||
typeBinding = getBindingAttr(el, 'type') | |||
} | |||
if (!typeBinding && map['v-bind']) { | |||
if (!map.type && !typeBinding && map['v-bind']) { |
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.
This would make following case lose type binding:
<input type="checkbox" v-model="test" v-bind="{type: typeBindingValue}">
So maybe
typeBinding = `(${map['v-bind']}).type || '${map.type}'`
EDIT: the one above is not comprehensive, while map.type
still could be undefined.
typeBinding = `(${map['v-bind']}).type || ${JSON.stringify(map.type)}`
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.
@hirokiosame If you could add the test as well, that would be great 👌
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 don't think we should allow v-bind
to override a static type
, it's gonna be confusing if done accidentally and I don't think there's a valid use case.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch for v2.x (or to a previous version branch), not themaster
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: