Errors on config comments suppressed about eslint-plugin-markdown HOT 6 CLOSED

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.

from eslint-plugin-markdown.

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.

from eslint-plugin-markdown.

Does this behavior cause #77?

from eslint-plugin-markdown.

And maybe also #78?

from eslint-plugin-markdown.

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.

from eslint-plugin-markdown.

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.

from eslint-plugin-markdown.