Include more operators in `no-mixed-operators`’s default config (by ESLint 8?)

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

Does this change cause the rule to produce more or fewer warnings?

More

How will the change be implemented? (New option, new default behavior, etc.)?

New default

Please provide some example code that this change will affect:

a || b === c
a ?? b === c

What does the rule currently do for this code?

No error, unless configured.

What will the rule do after it’s changed?

Suggest a fix:

a || (b === c)
a ?? (b === c)

Are you willing to submit a pull request to implement this change?

Possibly

[nzakas]

I can’t say I understand why the operators are grouped the way they are, but it does seem intentional and your config does seem to be the correct way to override the default.

[fregante]

make me think this is a bug in the rule’s default behavior

I didn’t say it’s a bug, it just said it would be helpful to enable more warnings. Since it’s a new operator, it’s not clear what the result of a ?? b === c would be.

Given that the behavior seems intentional

Intentional how? It just allows more operators being mixed. 🤷‍♂️ It’s as “intentional” as the lack of a rule. The operator did not exist when the rule was written.

given we’re already at v8.0.0-rc.0, that would mean v9.

That’s unfortunate, it would be a simple change to bring in v8, hence the issue title.