-
Notifications
You must be signed in to change notification settings - Fork 47k
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
Move null-input-value-prop warning into devtool, add stack trace #7040
Conversation
No tests? |
Tests still pass, they use toContain. Could change them to replace the stack trace with a dummy value and then assert the dummy value is there, but it didn't seem worth the effort. The important thing is that we are testing that the warning is firing (which we already test). |
var ReactComponentTreeDevtool = require('ReactComponentTreeDevtool'); | ||
|
||
var didWarnValueNull = false; | ||
var warning = require('warning'); |
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 reorder so requires come first with a blank line after?
Okay. |
6f9f6b7
to
0c14413
Compare
0c14413
to
deb4728
Compare
@jimfb updated the pull request. |
Moving this back to semver-patch. I think it's probably up for some interpretation if this is minor or patch but it'll make the release process easier if it's patch (conflicts in other patch PRs). The warning is just more informative so I'm inclined to say it's ok. |
(cherry picked from commit 97d89fa)
Move null-input-value-prop warning into devtool, add stack trace