{"action":"created","issue":{"url":"https://api.github.com/repos/jshint/jshint/issues/2575","labels_url":"https://api.github.com/repos/jshint/jshint/issues/2575/labels{/name}","comments_url":"https://api.github.com/repos/jshint/jshint/issues/2575/comments","events_url":"https://api.github.com/repos/jshint/jshint/issues/2575/events","html_url":"https://github.com/jshint/jshint/issues/2575","id":96302493,"number":2575,"title":"Provide a way to include warning messages in .jshintrc","user":{"login":"Adam-Moss","id":2951486,"avatar_url":"https://avatars.githubusercontent.com/u/2951486?v=3","gravatar_id":"","url":"https://api.github.com/users/Adam-Moss","html_url":"https://github.com/Adam-Moss","followers_url":"https://api.github.com/users/Adam-Moss/followers","following_url":"https://api.github.com/users/Adam-Moss/following{/other_user}","gists_url":"https://api.github.com/users/Adam-Moss/gists{/gist_id}","starred_url":"https://api.github.com/users/Adam-Moss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Adam-Moss/subscriptions","organizations_url":"https://api.github.com/users/Adam-Moss/orgs","repos_url":"https://api.github.com/users/Adam-Moss/repos","events_url":"https://api.github.com/users/Adam-Moss/events{/privacy}","received_events_url":"https://api.github.com/users/Adam-Moss/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jshint/jshint/labels/Has%20PR","name":"Has PR","color":"009800"},{"url":"https://api.github.com/repos/jshint/jshint/labels/Proposal","name":"Proposal","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-07-21T12:17:11Z","updated_at":"2015-07-23T17:25:06Z","closed_at":null,"body":"This is basically the opposite of #2551 in that I'd like to be able to include specific warnings in the .jshintrc.  For example if I have in my .jshintrc:\r\n\r\n    \"globalstrict\": false,\r\n    \"strict\": true,\r\n    \"node\": true\r\n\r\nThen the global strict warning W097 is effectively ignored.\r\n\r\nI've tried:\r\n\r\n    \"globalstrict\": false,\r\n    \"strict\": true,\r\n    \"node\": true,\r\n    \"predef\": [\r\n        \"-console\"\r\n      ],\r\n    \"+W097\": true\r\n\r\nWhich (based on #1922 and #2551) I believe should do what I'm looking to achieve but sadly doesn't."},"comment":{"url":"https://api.github.com/repos/jshint/jshint/issues/comments/124173768","html_url":"https://github.com/jshint/jshint/issues/2575#issuecomment-124173768","issue_url":"https://api.github.com/repos/jshint/jshint/issues/2575","id":124173768,"user":{"login":"Adam-Moss","id":2951486,"avatar_url":"https://avatars.githubusercontent.com/u/2951486?v=3","gravatar_id":"","url":"https://api.github.com/users/Adam-Moss","html_url":"https://github.com/Adam-Moss","followers_url":"https://api.github.com/users/Adam-Moss/followers","following_url":"https://api.github.com/users/Adam-Moss/following{/other_user}","gists_url":"https://api.github.com/users/Adam-Moss/gists{/gist_id}","starred_url":"https://api.github.com/users/Adam-Moss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Adam-Moss/subscriptions","organizations_url":"https://api.github.com/users/Adam-Moss/orgs","repos_url":"https://api.github.com/users/Adam-Moss/repos","events_url":"https://api.github.com/users/Adam-Moss/events{/privacy}","received_events_url":"https://api.github.com/users/Adam-Moss/received_events","type":"User","site_admin":false},"created_at":"2015-07-23T17:25:06Z","updated_at":"2015-07-23T17:25:06Z","body":"Actually having thought a bit more about this PR I'm not sure it's the right way to go.  If I read the JSHint options documentation at http://jshint.com/docs/options/ there are quite a few of the options being deprecated as they are not linting issues but rather stylistic choices.\r\n\r\nFollowing that thought train would therefore suggest the same should be applied to this requirement, as the current behaviour of jshint in this instance is to force a coding style in this scenario.\r\n\r\nSo the question would be therefore is the \"correct\" behaviour when specifying an environment in jshint for it to actually just define the globals associated with that environment rather than define the globals and some rules?  Because presumably the rules bit would be covered anyway if you set the relevant option?"}}