feat: new rule: sort-heritage-clauses
#334
Merged
+1,490
−20
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.
Description
This PR adds a
sort-heritage-clauses
(feel free to suggest another name if you find a better one) that allows users to sort classesimplements
and interfacesextends
clauses.Example:
Options
There is only one predefined group:
unknown
.I don't believe that
partitionByNewline
andpartitionByComment
have relevant use cases here.What is the purpose of this pull request?