-
-
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
Add slot v-bind warning (fix #6677) #6736
Conversation
v-bind with not object warning 6677
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.
Thanks for your contribution!
Could you add a simple test case that checks that the message is warned?
@@ -15,6 +15,12 @@ export function renderSlot ( | |||
if (scopedSlotFn) { // scoped slot | |||
props = props || {} | |||
if (bindObject) { | |||
if (!isObject(bindObject)) { | |||
process.env.NODE_ENV !== 'production' && warn( |
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.
can you move the process.env.NODE_ENV !== 'production'
into the if condition so it gets stripped off in production mode?
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.
Oh, of course I can move it!
Sure, I will add the test.
Ready to merge :) |
v-bind with not object warning
close #6677
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: