Fix findDOMNode lint warning #5993
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Ignore the warning we get for using findDOMNode - Explain why we're ignoring the warning - Make this warning an error so that CI picks this up in the future
ntwb
approved these changes
Apr 5, 2018
aduth
reviewed
Apr 5, 2018
| @@ -114,7 +114,6 @@ module.exports = { | |||
| 'react/jsx-key': 'error', | |||
| 'react/jsx-tag-spacing': 'error', | |||
| 'react/no-children-prop': 'off', | |||
| 'react/no-find-dom-node': 'warn', | |||
There was a problem hiding this comment.
To the future casual observer, this is defined in the React recommended preset we extend as an error already. We were previously downgrading to warn:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #4115 (comment).
findDOMNodefindDOMNodefindDOMNode🐶