{"action":"created","issue":{"url":"https://api.github.com/repos/eslint/eslint/issues/2100","labels_url":"https://api.github.com/repos/eslint/eslint/issues/2100/labels{/name}","comments_url":"https://api.github.com/repos/eslint/eslint/issues/2100/comments","events_url":"https://api.github.com/repos/eslint/eslint/issues/2100/events","html_url":"https://github.com/eslint/eslint/issues/2100","id":62719544,"number":2100,"title":"Reset all rules from .eslintrc","user":{"login":"mickaeltr","id":378910,"avatar_url":"https://avatars.githubusercontent.com/u/378910?v=3","gravatar_id":"","url":"https://api.github.com/users/mickaeltr","html_url":"https://github.com/mickaeltr","followers_url":"https://api.github.com/users/mickaeltr/followers","following_url":"https://api.github.com/users/mickaeltr/following{/other_user}","gists_url":"https://api.github.com/users/mickaeltr/gists{/gist_id}","starred_url":"https://api.github.com/users/mickaeltr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mickaeltr/subscriptions","organizations_url":"https://api.github.com/users/mickaeltr/orgs","repos_url":"https://api.github.com/users/mickaeltr/repos","events_url":"https://api.github.com/users/mickaeltr/events{/privacy}","received_events_url":"https://api.github.com/users/mickaeltr/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eslint/eslint/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-03-18T15:17:47Z","updated_at":"2015-04-09T15:58:29Z","closed_at":null,"body":"Hello,\r\n\r\nI have the following use case:\r\n- prevent the use of console.* calls in the whole codebase\r\n- in a specific folder, check all default eslint rules + some specific rules\r\n\r\nSo what I first did is call `eslint --reset` with:\r\n- a simple .eslintrc at the root, with `{\"rules\": {\"no-console\": 2}}` only\r\n- a .eslintrc in the specific folder, with some specific rules\r\n\r\nThe problem is that the `--reset` flag prevents from applying the default eslint rules on the specific folders.\r\n\r\nI see 3 options:\r\n1. Call eslint twice: one time with `--reset`, another time on the specific folder with `--reset`\r\n2. Disable all rules manually in the root .eslintrc\r\n3. Enable all rules manually in the specific folder .eslintrc\r\n\r\nThose options are not really desirable, so I am thinking that it would be nice to be able to reset all rules in the .eslintrc file, so it could be overriden by more specific configuration files below.\r\n\r\nWhat do you think?"},"comment":{"url":"https://api.github.com/repos/eslint/eslint/issues/comments/91273115","html_url":"https://github.com/eslint/eslint/issues/2100#issuecomment-91273115","issue_url":"https://api.github.com/repos/eslint/eslint/issues/2100","id":91273115,"user":{"login":"nzakas","id":38546,"avatar_url":"https://avatars.githubusercontent.com/u/38546?v=3","gravatar_id":"","url":"https://api.github.com/users/nzakas","html_url":"https://github.com/nzakas","followers_url":"https://api.github.com/users/nzakas/followers","following_url":"https://api.github.com/users/nzakas/following{/other_user}","gists_url":"https://api.github.com/users/nzakas/gists{/gist_id}","starred_url":"https://api.github.com/users/nzakas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nzakas/subscriptions","organizations_url":"https://api.github.com/users/nzakas/orgs","repos_url":"https://api.github.com/users/nzakas/repos","events_url":"https://api.github.com/users/nzakas/events{/privacy}","received_events_url":"https://api.github.com/users/nzakas/received_events","type":"User","site_admin":false},"created_at":"2015-04-09T15:58:29Z","updated_at":"2015-04-09T15:58:29Z","body":"The problem is that configs cascade, so resetting in one config could affect others. We apply the reset before the first config is read, and then use each subsequent config to override those settings. If we allow reset in a config, then at any point all previous configs will be blown away. This is why it must be an option on the command line - it would completely break config cascade."}}