Add "fix" severity level

ESLint is smart enough to auto fix some of the code. The problem is, in order to do so, the related rule must be marked as "warn" or "error", which can pollute the code with unnecessary warnings. For example: indent - good rule, but produces too much warnings/errors, that can be solved easily with CI (let’s ignore prettier for this example).

My proposition is to have additional "fix" level that does not produce an error/warning, but is still auto fixed when running with --fix.

One possible problem would be if the user configures non-fixable rule as "fix" - what would happen then? Maybe then it should not be a severity level, but something else that suppresses the error/warning? Or simply interpret is as "off"?

[TehShrike]

I’m looking for a solution to this problem as well.

I don’t want to see visual warnings in my IDE for things that eslint is going to automatically fix for me as soon as I hit the save button.

I currently solve this by putting my fixable rules in one config file, and the rules that I want to affect my IDE in another config file. This is pretty jankety.

[kaicataldo]

Feel free to open a new issue with a proposal if this is something you’d like to advocate for. My comments above still stand!