Feature Request: `info` severity level

I love that ESLint supports multiple severity levels. This is a huge advantage over many other linters. I’d love to see this developed a little further. I think adding an additional info severity level would be a good improvement. Basically this would be a less severe than ‘warn’ . It would be used to notify about common issues that you don’t want enforced and treated as a failure.

So the levels would look like this:

• error: should be fixed immediately (pseudo compile-time error)
• warn: may be ignored during prototyping, but should be fixed or disabled before committing
• info: notify the developer, but don’t want to enforce
• off

There’s secondary benefit to info as well. If a rule does not totally conform to your standards (for me curly is an example), setting the rule to info would allow you reap some benefit from the rule without having to update all of your code.

[kasperpeulen]

Just saying, that I would also really love an extra level. All the argument against this seem with the idea that eslint is mostly used on the command line. But if you use it in an editor, it is very common and useful to have more levels of severity.

[ben-page]

The difference is only in how people interact with the output. Basically, a file containing info messages would “pass” and files with warn messages would fail. It’s especially helpful when using ESLint in an editor. error and warn messages should be intrusive to encourage them to be fixed, info messages should not be intrusive. This is how the built-in inspections in most IDEs work.