Why is no-mixed-operators deprecated / stylistic? #18408
-
Hi all, I noticed the no-mixed-operators rule has been deprecated in favour of the stylistic equivolent, I'm just wondering what the rationale is for considering it "stylistic" ? Operator precedence is a common cause of bugs and it's an easy mistake to make. Adding parenthesis goes beyond a styling decision, it's used to make the developer's intention clear at a glance without having to worry about memorising the precedence of each operator in Javascript. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Indeed, we didn't consider this rule as just stylistic, Please see the discussion in #17522 for the rationale for deprecating this rule in the core and moving it to the stylistic plugin (in particular, #17522 (comment) and #17522 (comment)). |
Beta Was this translation helpful? Give feedback.
Indeed, we didn't consider this rule as just stylistic, Please see the discussion in #17522 for the rationale for deprecating this rule in the core and moving it to the stylistic plugin (in particular, #17522 (comment) and #17522 (comment)).