-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
More robust no typos fix #1375
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
Merged
yannickcr
merged 6 commits into
jsx-eslint:master
from
jseminck:more-robust-no-typos-fix
Aug 21, 2017
Merged
More robust no typos fix #1375
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1301fe9
More robust no-typos fix
fa890cb
Tests and explaining the case that is currently not supported.
1292807
Add comment explaining try/catch
0cf2415
Add comment to the eslint parent definition issue
d00e9e6
Remove FIXME as it fails linting
jseminck 5e25a5e
Re-add FIXME and disable the warning through eslint-disable-next-line
jseminck File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
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.
What about changing the places calling this method to be ":exit"?
Uh oh!
There was an error while loading. Please reload this page.
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.
It does not help. The
relatedComponent
(in the case below it isclass MyComponent
) is not a child in the AST of theMemberExpression
"MyComponent.PROPTYPES
" - so using:exit
does not work.The reason is just that
class MyComponent
is declared afterMyComponent.PROPTYPES
and therefore eslint has not yet visited it, and therefore it does not have theparent
property yet (whichgetJSDocComment()
expects to exist).They have a task to add parent property to all nodes on initial traversal, that would fix our issue.