Errors on config comments suppressed

[vsemozhetbyt]

From .eslintrc.js:

    strict: ['error', 'global'],
    'unicode-bom': ['error', 'always'],

Test doc 1:

Text

```js
console.log('a');
```

Result 1:

  4:1  error  Use the global form of 'use strict'     strict
  4:1  error  Expected Unicode BOM (Byte Order Mark)  unicode-bom

Test doc 2:

Text

<!-- eslint-disable strict -->
```js
console.log('a');
```

Result 2:

[No errors]

1. Maybe unicode-bom should be included in unsatisfiable rules.
2. Why eslint-disable any-other-rule comment also cancels unicode-bom?

[btmills]

Maybe unicode-bom should be included in unsatisfiable rules.

Agreed. I'll do that soon.

Why eslint-disable any-other-rule comment also cancels unicode-bom?

The config comment gets transformed and inserted into the code, so what gets linted looks like this:

/* eslint-disable strict */
console.log('a');

The unicode-bom rule still throws an error on line 1, column 1, but the plugin silences all errors thrown on the generated config comments since they're supposed to be invisible.

[vsemozhetbyt]

Does this behavior cause #77?

[vsemozhetbyt]

And maybe also #78?

[btmills]

I opened #84 to add unicode-bom to the list of unsatisfiable rules. I renamed this issue and will leave it open to see if there's anything that can be done about errors on config comments pulled in from HTML being suppressed.

[btmills]

Without digging in yet, I suspect at least one of #77 or #78 will be due to the parser truncating empty lines from the beginning of code blocks, which would be unrelated.

[btmills]

I believe the other cases here have been addressed, and I'll close this to track the remaining portion in #115, which I suspect has the same underlying cause.