You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XO currently just uses the rule’s default, but a change to it was rejected because it would be breaking.
Example config:
'no-mixed-operators': ['error',{// Customize the defaults to force being explicit about use of null-coalescing operator because its precedence// is unintuitive. See: https://eslint.org/docs/rules/no-mixed-operatorsgroups: [// Conflicts with Prettier: https://github.com/prettier/prettier/issues/3968// ["+", "-", "*", "/", "%", "**", "??"],['&','|','^','~','<<','>>','>>>','??'],['==','!=','===','!==','>','>=','<','<=','??'],['&&','||','??'],['in','instanceof','??'],],},],
Originally posted in eslint/eslint#14975
What rule do you want to change?
no-mixed-operators
:https://github.com/eslint/eslint/blob/c981fb1994cd04914042ced1980aa86b68ba7be9/lib/rules/no-mixed-operators.js#L25-L40
Please provide some example code that this change will affect:
What will the rule do after it's changed?
Suggest a fix:
The text was updated successfully, but these errors were encountered: