{"action":"closed","issue":{"url":"https://api.github.com/repos/eslint/eslint/issues/2993","labels_url":"https://api.github.com/repos/eslint/eslint/issues/2993/labels{/name}","comments_url":"https://api.github.com/repos/eslint/eslint/issues/2993/comments","events_url":"https://api.github.com/repos/eslint/eslint/issues/2993/events","html_url":"https://github.com/eslint/eslint/issues/2993","id":94959051,"number":2993,"title":"lint-disable instead of eslint-disable","user":{"login":"denis-sokolov","id":113721,"avatar_url":"https://avatars.githubusercontent.com/u/113721?v=3","gravatar_id":"","url":"https://api.github.com/users/denis-sokolov","html_url":"https://github.com/denis-sokolov","followers_url":"https://api.github.com/users/denis-sokolov/followers","following_url":"https://api.github.com/users/denis-sokolov/following{/other_user}","gists_url":"https://api.github.com/users/denis-sokolov/gists{/gist_id}","starred_url":"https://api.github.com/users/denis-sokolov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/denis-sokolov/subscriptions","organizations_url":"https://api.github.com/users/denis-sokolov/orgs","repos_url":"https://api.github.com/users/denis-sokolov/repos","events_url":"https://api.github.com/users/denis-sokolov/events{/privacy}","received_events_url":"https://api.github.com/users/denis-sokolov/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eslint/eslint/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-14T14:37:54Z","updated_at":"2015-07-14T14:50:23Z","closed_at":"2015-07-14T14:50:23Z","body":"Consider adding and promoting the use of `/* lint-disable */` instead of `/* eslint-disable */`.\r\nOf course, the support for the old name should stay, but not be under the spotlight anymore.\r\n\r\nThe information that the author wants to allow using `console` or `eval` in this particular piece of code is semantically valuable regardless of the particular brand of the linting tool used.\r\n\r\nGeneralizing the comment name might allow for a wider variety of linting tools, while keeping the directive branded puts potential pressure on other engine authors to interpret eslint-specific directives, similarly to Webkit CSS prefixes issue.\r\nIt would also allow for more pleasant sharing of code. Sharing a snippet with an `eslint`-branded comment implies the person receiving it cares about eslint. A non-branded directive would instead be treated as a nice note in the code even if not used directly.\r\n\r\nI recognize that the proposal is unlikely to be accepted, but I thought this concern should be addressed before the 1.0.0 release."}}