-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Flow 0.53 support #1377
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
Merged
Flow 0.53 support #1377
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
3e85c55
Attempt at Flow 0.53 support
jseminck 585b94a
Add invalid test case
jseminck f767f68
Add support and test for custom props name
jseminck deb3b61
Add invalid test case for custom prop names
jseminck 1a8af56
Revert old implementation and replace by configurable flowVersion
jseminck d232811
Remove flow version and decide the Props argument location based on t…
jseminck 1ebfcee
Add flowVersion back but without a default. When there is no flow ver…
jseminck a7957a1
update readme regarding the flowVersion setting
jseminck 18ad186
Fix bug and add tests through helper function
jseminck bb0a457
Add explicit > check for params length
jseminck cd96ec9
remove test helper function as we cannot use spread operator
jseminck 6d1b7f1
Add one more test case for the new syntax
jseminck a6d26d9
Move flowVersion setting in invalid tests closer to the code
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
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
Oops, something went wrong.
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.
doesn't this mean that if it's not specified, it throws?
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.
Yes. That's what we wanted, right?
We don't want to provide a default value, so
test()
cannot returntrue
orfalse
in case it is not specified. Therefore, throwing an exception instead which we then handle in the calling code by catching it and using the default logic.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.
Sorry if I wasn't clear; when no version is specified, I want the logic to be "guess which flowVersion it is" - specifying a flow version can't be required, or else it's a very large breaking change.
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.
We are guessing what the flowVersion is, but only for the specific implementation in the
prop-types
rule: https://github.com/yannickcr/eslint-plugin-react/pull/1377/files#diff-531a13f7edd3ed4e7c65c3a7df7052f0R868As this is a general utility function, I don't think that here we can easily guess what flow version we are using, because we need more information about the code. In the
prop-types
example, we need to know how manyTypedArguments
there are. But if there are none, then we cannot make a guess. If another rule would want to use this utility function, they would have to specify their own criteria/logic for guessing the correct flowVersion.I can move this utility function into the
prop-types
rule directly, as it is currently the only place where it is used. I just thought that for future cases it might be good to have it extracted already, so that it can be used in other rules as well.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.
Ah, i see what you mean.
I guess that's OK, but i feel like maybe returning
null
here would be easier to deal with than try/catch.