[Fix] no-unused-prop-types with typescript eslint parser #2661
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
Fixes jsx-eslint#2569. Co-authored-by: Antoine <antoine.sauvage@melix.net> Co-authored-by: Jordan Harband <ljharb@gmail.com>
ljharb
requested changes
Jun 7, 2020
|
ok I pushed a new version with :
|
|
ok, I don't get how to make flatmap work :( |
|
@eltonio450 i can fix the branch, but since you made the PR from |
|
done :) thank you :) |
|
thank you ! |
|
no no, thank you! |
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.
Hi there,
This is a first draft to solve #2569
I would be thankful if someone involved in this rule creation could give feedback about edge cases to be handled (spread operator, etc.). I am afraid to have forgotten some...
Thank you !