{"action":"created","issue":{"url":"https://api.github.com/repos/eslint/eslint.github.io/issues/282","repository_url":"https://api.github.com/repos/eslint/eslint.github.io","labels_url":"https://api.github.com/repos/eslint/eslint.github.io/issues/282/labels{/name}","comments_url":"https://api.github.com/repos/eslint/eslint.github.io/issues/282/comments","events_url":"https://api.github.com/repos/eslint/eslint.github.io/issues/282/events","html_url":"https://github.com/eslint/eslint.github.io/issues/282","id":171185896,"number":282,"title":"Rules: \"no-template-curly-in-string\" is listed in the wrong section of the page","user":{"login":"mateatslc","id":590577,"avatar_url":"https://avatars.githubusercontent.com/u/590577?v=3","gravatar_id":"","url":"https://api.github.com/users/mateatslc","html_url":"https://github.com/mateatslc","followers_url":"https://api.github.com/users/mateatslc/followers","following_url":"https://api.github.com/users/mateatslc/following{/other_user}","gists_url":"https://api.github.com/users/mateatslc/gists{/gist_id}","starred_url":"https://api.github.com/users/mateatslc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mateatslc/subscriptions","organizations_url":"https://api.github.com/users/mateatslc/orgs","repos_url":"https://api.github.com/users/mateatslc/repos","events_url":"https://api.github.com/users/mateatslc/events{/privacy}","received_events_url":"https://api.github.com/users/mateatslc/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eslint/eslint.github.io/labels/triage","name":"triage","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-15T14:50:19Z","updated_at":"2016-08-15T14:55:21Z","closed_at":null,"body":"`no-template-curly-in-string` introduced in v3.3.0 is listed under the http://eslint.org/docs/rules/#possible-errors section currently.\r\nAs it is purely ES6 related I feel it should be moved over to the http://eslint.org/docs/rules/#ecmascript-6 section of the page."},"comment":{"url":"https://api.github.com/repos/eslint/eslint.github.io/issues/comments/239823498","html_url":"https://github.com/eslint/eslint.github.io/issues/282#issuecomment-239823498","issue_url":"https://api.github.com/repos/eslint/eslint.github.io/issues/282","id":239823498,"user":{"login":"platinumazure","id":284282,"avatar_url":"https://avatars.githubusercontent.com/u/284282?v=3","gravatar_id":"","url":"https://api.github.com/users/platinumazure","html_url":"https://github.com/platinumazure","followers_url":"https://api.github.com/users/platinumazure/followers","following_url":"https://api.github.com/users/platinumazure/following{/other_user}","gists_url":"https://api.github.com/users/platinumazure/gists{/gist_id}","starred_url":"https://api.github.com/users/platinumazure/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/platinumazure/subscriptions","organizations_url":"https://api.github.com/users/platinumazure/orgs","repos_url":"https://api.github.com/users/platinumazure/repos","events_url":"https://api.github.com/users/platinumazure/events{/privacy}","received_events_url":"https://api.github.com/users/platinumazure/received_events","type":"User","site_admin":false},"created_at":"2016-08-15T14:55:21Z","updated_at":"2016-08-15T14:55:21Z","body":"So the real question here seems to be, should all ES6 syntax rules go into the ES6 category, or can a different category be more appropriate depending on the nature of the rule?\r\n\r\nIt is definitely the case that the rule is for flagging a (pretty subtle) possible error.\r\n\r\nPersonally I'm wondering if there needs to be one definitive category for a rule (possible error vs best practice vs style) and then other flags (is it ES6 only? Is it primarily about variables? etc.) could be added. But that might be a deeper discussion than @mateatslc had in mind."}}
{"actor":{"display_login":"platinumazure"}}