{"action":"created","issue":{"url":"https://api.github.com/repos/SublimeLinter/SublimeLinter/issues/691","repository_url":"https://api.github.com/repos/SublimeLinter/SublimeLinter","labels_url":"https://api.github.com/repos/SublimeLinter/SublimeLinter/issues/691/labels{/name}","comments_url":"https://api.github.com/repos/SublimeLinter/SublimeLinter/issues/691/comments","events_url":"https://api.github.com/repos/SublimeLinter/SublimeLinter/issues/691/events","html_url":"https://github.com/SublimeLinter/SublimeLinter/issues/691","id":280852768,"number":691,"title":"Base linter selection on scope instead of syntax file name","user":{"login":"FichteFoll","id":931051,"avatar_url":"https://avatars1.githubusercontent.com/u/931051?v=4","gravatar_id":"","url":"https://api.github.com/users/FichteFoll","html_url":"https://github.com/FichteFoll","followers_url":"https://api.github.com/users/FichteFoll/followers","following_url":"https://api.github.com/users/FichteFoll/following{/other_user}","gists_url":"https://api.github.com/users/FichteFoll/gists{/gist_id}","starred_url":"https://api.github.com/users/FichteFoll/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/FichteFoll/subscriptions","organizations_url":"https://api.github.com/users/FichteFoll/orgs","repos_url":"https://api.github.com/users/FichteFoll/repos","events_url":"https://api.github.com/users/FichteFoll/events{/privacy}","received_events_url":"https://api.github.com/users/FichteFoll/received_events","type":"User","site_admin":false},"labels":[{"id":62150693,"url":"https://api.github.com/repos/SublimeLinter/SublimeLinter/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2017-12-10T22:38:11Z","updated_at":"2018-02-19T18:37:38Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Basing the linter selection on the base scope is much more flexible as opposed to having a large `syntax_map` mapping, since most JavaScript-like languages *will* be using `source.js` as the base scope and possibly add more leaves to that, e.g. `source.js.babel`. Or `source.json.sublime.settings`.\r\n\r\nKind of nullifies #431 too, since all use cases I had in mind for that would be solved by this solution.\r\n\r\nTo outline the extend of this problem, this is my current `syntax_map` settings (which I didn't even realize to have grown so much – probably the work of a plugin, and I suspect a theme providing icons, like @ihodev's A File Icon):\r\n\r\n```\r\n    \"syntax_map\": {\r\n        \"coffeescript (gulpfile)\": \"coffeescript\",\r\n        \"html (django)\": \"html\",\r\n        \"html (rails)\": \"html\",\r\n        \"html 5\": \"html\",\r\n        \"javascript (babel)\": \"javascript\",\r\n        \"javascript (eslint)\": \"javascript\",\r\n        \"javascript (gruntfile)\": \"javascript\",\r\n        \"javascript (gulpfile)\": \"javascript\",\r\n        \"javascript (postcss)\": \"javascript\",\r\n        \"javascript (stylelint)\": \"javascript\",\r\n        \"javascript (webpack)\": \"javascript\",\r\n        \"json\": \"javascript\",\r\n        \"json (babel)\": \"json\",\r\n        \"json (bower)\": \"json\",\r\n        \"json (composer)\": \"json\",\r\n        \"json (eslint)\": \"json\",\r\n        \"json (npm)\": \"json\",\r\n        \"json (postcss)\": \"json\",\r\n        \"json (settings)\": \"json\",\r\n        \"json (stylelint)\": \"json\",\r\n        \"json (sublime)\": \"json\",\r\n        \"json (tern js)\": \"json\",\r\n        \"php\": \"html\",\r\n        \"python django\": \"python\",\r\n        \"sublime commands\": \"javascript\",\r\n        \"sublime completions\": \"javascript\",\r\n        \"sublime key map\": \"javascript\",\r\n        \"sublime macros\": \"javascript\",\r\n        \"sublime settings\": \"javascript\",\r\n        \"sublime text build system\": \"javascript\",\r\n        \"sublime text syntax def (json)\": \"javascript\",\r\n        \"sublime text syntax def (yaml)\": \"yaml\",\r\n        \"xml (config)\": \"xml\",\r\n        \"xml (svg)\": \"xml\",\r\n        \"yaml\": \"yaml\",\r\n        \"yaml (circleci)\": \"yaml\",\r\n        \"yaml (docker)\": \"yaml\",\r\n        \"yaml (eslint)\": \"yaml\",\r\n        \"yaml (lock)\": \"yaml\",\r\n        \"yaml (procfile)\": \"yaml\",\r\n        \"yaml (stylelint)\": \"yaml\",\r\n        \"yaml (yarn)\": \"yaml\"\r\n    },\r\n```"},"comment":{"url":"https://api.github.com/repos/SublimeLinter/SublimeLinter/issues/comments/366773841","html_url":"https://github.com/SublimeLinter/SublimeLinter/issues/691#issuecomment-366773841","issue_url":"https://api.github.com/repos/SublimeLinter/SublimeLinter/issues/691","id":366773841,"user":{"login":"braver","id":2543659,"avatar_url":"https://avatars1.githubusercontent.com/u/2543659?v=4","gravatar_id":"","url":"https://api.github.com/users/braver","html_url":"https://github.com/braver","followers_url":"https://api.github.com/users/braver/followers","following_url":"https://api.github.com/users/braver/following{/other_user}","gists_url":"https://api.github.com/users/braver/gists{/gist_id}","starred_url":"https://api.github.com/users/braver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/braver/subscriptions","organizations_url":"https://api.github.com/users/braver/orgs","repos_url":"https://api.github.com/users/braver/repos","events_url":"https://api.github.com/users/braver/events{/privacy}","received_events_url":"https://api.github.com/users/braver/received_events","type":"User","site_admin":false},"created_at":"2018-02-19T18:37:38Z","updated_at":"2018-02-19T18:37:38Z","author_association":"OWNER","body":"Wouldn’t that be solved via user defined syntaxes (#994)? I.e. a user would enable eslint for the text.html scope."}}
{"actor":{"display_login":"braver"}}