We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the current implementation there are two forms of violations that can cause redundant errors.
Given an expected order of [ a, b, c ], and an actual order of [ b, c, a ], the rule will currently report 2 errors:
[ a, b, c ]
[ b, c, a ]
The second error is redundant and should not be reported.
Given an expected order of [ a, b, c ], and an actual order of [ c, a, b ], the rule will currently report 2 errors:
[ c, a, b ]
This can be more succinctly reported as a single error: "expected c to come after b".
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In the current implementation there are two forms of violations that can cause redundant errors.
Members appearing multiple positions late
Given an expected order of
[ a, b, c ]
, and an actual order of[ b, c, a ]
, the rule will currently report 2 errors:The second error is redundant and should not be reported.
Members appearing multiple positions early
Given an expected order of
[ a, b, c ]
, and an actual order of[ c, a, b ]
, the rule will currently report 2 errors:This can be more succinctly reported as a single error: "expected c to come after b".
The text was updated successfully, but these errors were encountered: