eslint comments to enable/disable not respecting order specified in code

/*eslint camelcase: 0*/
var queryParams = {
    first_param: 'foo'
};
queryParams.second_param = 'bar';
/*eslint camelcase: 1*/

  3:1   warning  Identifier 'first_param' is not in camel case   camelcase
  5:12  warning  Identifier 'second_param' is not in camel case  camelcase
✖ 2 problems

It looks like the second /*eslint*/ comment takes precedence. Default rule is camelcase: 2. If I remove the second /*eslint*/ comment, no errors are thrown.

Use Case: Legacy APIs sometimes use underscores for params.

I’ve also verified this is the case with other rules as well.

[nzakas]

It’s not possible to change rules like that. Basically, ESLint goes through and finds all comments that of the form /*eslint foo:0*/ before it starts parsing and evaluating the code. If you want to turn off rules for a particular piece of code, you need to use /*eslint-disable*/ and /*eslint-enable*/ to turn it back on:

/*eslint-disable camelcase*/
var queryParams = {
    first_param: 'foo'
};
queryParams.second_param = 'bar';
/*eslint-enable camelcase*/

[calidion]

@platinumazure

I have solved by the following code.

/*eslint camelcase: [2, {properties: "never"}]*/

it seems the rules are changed.