Disable no-mixed-operators rule

Please consider adding options in the config to disable (or add) certain linting rules. The default options are very aggressive and I end up with a lot of warnings both in command line output and in browser console. My main nemesis is no-mixed-operators, since I often use the x && y || z construct as an alternative to ternary operator. It is too common to put disable comments every time.

I can comment out the rules in the plugin, but that doesn’t seem to be a good solution since it won’t work well with updates.

On a side note, what are the implications of ejecting? The manual doesn’t make that very clear. I understand that I can’t go back to “managed” state, but what are the benefits of staying in that state?

[matthewdaniel]

I compile typescript into the src folder which react-scripts then picks up.

IMO the rules should be setup in such a way as to support generated code.

[hielfx]

I think you can disable it adding a .eslintrc file in the project root folder and overwritting the create-react-app default rules like this:

{
  "extends": "react-app",
  "rules": {
   "no-mixed-operators": 0 // <- turn the eslint rule off by adding "off" or 0
  }
}

Hope this helps