should throw an error when disabling a non-existent rule

Tell us about your environment

• **ESLint Version:**master
• Node Version:
• npm Version:

What parser (default, Babel-ESLint, etc.) are you using? default

What did you do? Please include the actual source code causing the issue.

/* eslint foo: 0 */

// edit: or in a config file
{
  "rules": { "foo": 0}
}

What did you expect to happen? throw an error, since there is no rule named foo. What actually happened? Please include the actual, raw output from ESLint. no error thrown.

[platinumazure]

TSC Summary: The main issue is that if a rule is disabled, either in a config file or in an inline comment, the disable would silently do nothing and the user would never know. We thought this would be a problem for end users, but Jordan Harband pointed out that this has a large negative effect on plugin maintainers that want to support multiple versions of ESLint. This issue was originally created and accepted as a bug and I don’t believe sufficient discussion has occurred that takes into account the negative side effects of the original design. I believe this should not be in 6.0.0 and that this needs more discussion, possibly even an RFC.

TSC Question: Should we remove this from 6.0.0 and ask for further design discussion? As an ancillary question, should we require an RFC for this change?

[sstern6]

thanks @kaicataldo Ill hold off. Plenty of other stuff I can get done.