Avoid conflict: no-mixed-operators / no-extra-parens
#8
Conversation
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
|
@fredden please add a changelog :) |
The documentation for 'no-mixed-operators' states: > This rule may conflict with no-extra-parens rule. If you use both this and > no-extra-parens rule together, you need to use the nestedBinaryExpressions > option of no-extra-parens rule.
fredden
force-pushed
the
eslint-conflict
branch
from
5fa0212 to
b63d49a
Compare
leonhelmus
approved these changes
Oct 17, 2022
|
Released with tag |
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.
The documentation for 'no-mixed-operators' states:
https://eslint.org/docs/latest/rules/no-mixed-operators
https://eslint.org/docs/latest/rules/no-extra-parens