Cannot overwrite rule options from sharable config

What version of ESLint are you using? v2.9.0

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

Please show your full configuration: my eslint-es5.js:

{
  extends: ['airbnb-base/legacy'],
  rules: {
    'eqeqeq': 'error'
  }
}

Relevant part of airbnb-base/legacy.js:

{
  rules: {
    'eqeqeq': ['error', 'allow-null']
  }
}

What did you expect to happen? I expected there to be a way to overwrite this ‘allow-null’ exception because I want to enforce eqeqeq at all times.

What actually happened? Please include the actual, raw output from ESLint. I am still able to do bool == null.

[platinumazure]

I’m not sure I agree with the logic that (in the OP’s example) allow-null option should remain. I believe we should have configuration be all-or-nothing at the rule level-- if a rule is specified in derived config, it is assumed to be a full configuration that completely replaces the configuration specified in base config file.

Note that this still allows for the most common cases (derived config turns off rule enabled in base config, derived config turns on rule disabled in base config) to continue to work as they always have. In the case of derived config turning a rule on, the derived config must already specify a full and valid configuration.

In the case described by OP, we have an example of configuration being implicit in the derived configuration file. That strikes me as violating the principle of least surprise and I think we should change it, even if it’s a breaking change.

[alberto]

I think there should be an explicit default option for eqeqeq