{"action":"created","issue":{"url":"https://api.github.com/repos/eslint/eslint/issues/6139","repository_url":"https://api.github.com/repos/eslint/eslint","labels_url":"https://api.github.com/repos/eslint/eslint/issues/6139/labels{/name}","comments_url":"https://api.github.com/repos/eslint/eslint/issues/6139/comments","events_url":"https://api.github.com/repos/eslint/eslint/issues/6139/events","html_url":"https://github.com/eslint/eslint/issues/6139","id":154297579,"number":6139,"title":"Feature Request: `info` severity level","user":{"login":"ben-page","id":744035,"avatar_url":"https://avatars.githubusercontent.com/u/744035?v=3","gravatar_id":"","url":"https://api.github.com/users/ben-page","html_url":"https://github.com/ben-page","followers_url":"https://api.github.com/users/ben-page/followers","following_url":"https://api.github.com/users/ben-page/following{/other_user}","gists_url":"https://api.github.com/users/ben-page/gists{/gist_id}","starred_url":"https://api.github.com/users/ben-page/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ben-page/subscriptions","organizations_url":"https://api.github.com/users/ben-page/orgs","repos_url":"https://api.github.com/users/ben-page/repos","events_url":"https://api.github.com/users/ben-page/events{/privacy}","received_events_url":"https://api.github.com/users/ben-page/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eslint/eslint/labels/question","name":"question","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2016-05-11T17:23:04Z","updated_at":"2016-05-11T20:17:33Z","closed_at":null,"body":"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.\r\n\r\nSo the levels would look like this:\r\n* `error`: should be fixed immediately (pseudo compile-time error)\r\n* `warn`: may be ignored during prototyping, but should be fixed or disabled before committing\r\n* `info`: notify the developer, but don't want to enforce\r\n* `off`\r\n\r\nThere'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.\r\n"},"comment":{"url":"https://api.github.com/repos/eslint/eslint/issues/comments/218577059","html_url":"https://github.com/eslint/eslint/issues/6139#issuecomment-218577059","issue_url":"https://api.github.com/repos/eslint/eslint/issues/6139","id":218577059,"user":{"login":"markelog","id":945528,"avatar_url":"https://avatars.githubusercontent.com/u/945528?v=3","gravatar_id":"","url":"https://api.github.com/users/markelog","html_url":"https://github.com/markelog","followers_url":"https://api.github.com/users/markelog/followers","following_url":"https://api.github.com/users/markelog/following{/other_user}","gists_url":"https://api.github.com/users/markelog/gists{/gist_id}","starred_url":"https://api.github.com/users/markelog/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/markelog/subscriptions","organizations_url":"https://api.github.com/users/markelog/orgs","repos_url":"https://api.github.com/users/markelog/repos","events_url":"https://api.github.com/users/markelog/events{/privacy}","received_events_url":"https://api.github.com/users/markelog/received_events","type":"User","site_admin":false},"created_at":"2016-05-11T20:17:33Z","updated_at":"2016-05-11T20:17:33Z","body":"If we would want to do this, i would implement the whole RFC5424 syslog levels maybe even with ability to define your own levels, but i really don't see the point so -1. "}}