Skip to content
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

Merged
merged 1 commit into from
Jun 14, 2016

Conversation

jimfb
Copy link
Contributor

@jimfb jimfb commented Jun 14, 2016

Move null-input-value-prop warning into devtool, add stack trace

@jimfb
Copy link
Contributor Author

jimfb commented Jun 14, 2016

@spicyj

@sophiebits
Copy link
Collaborator

No tests?

@jimfb
Copy link
Contributor Author

jimfb commented Jun 14, 2016

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');
Copy link
Collaborator

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?

@sophiebits
Copy link
Collaborator

Okay.

@ghost
Copy link

ghost commented Jun 14, 2016

@jimfb updated the pull request.

@jimfb jimfb merged commit 97d89fa into facebook:master Jun 14, 2016
@jimfb jimfb mentioned this pull request Jun 16, 2016
@zpao zpao added this to the 15-next milestone Jul 7, 2016
@zpao
Copy link
Member

zpao commented Jul 8, 2016

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.

zpao pushed a commit that referenced this pull request Jul 8, 2016
@zpao zpao modified the milestones: 15-next, 15.2.1 Jul 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants