Add requiredFirst
option to jsx-sort-prop-types
#392
Merged
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.
Hey there, I've been really enjoying
eslint-plugin-react
, thanks for creating such a great set of React rules for ESLint!Our team likes to put required prop type declarations first, followed by optional prop types. I extended the existing
jsx-sort-prop-types
rule to take arequiredFirst
option to make this enforceable by ESLint.When set to
true
required props must come first and be sorted alphabetically:In addition to the changes this PR includes tests and documentation.
Figured others could find it useful too. 😃