Getting it to work in VSCode? about eslint-plugin-markdown HOT 4 CLOSED

I finally figured out what was causing this! Most ESLint rules pass both start and end locations, but parse errors only specify start locations. A bug was causing the processor to add endLine: NaN to those messages, which was understandably confusing VSCode. I opened #154 to fix this.

from eslint-plugin-markdown.

I'm able to reproduce something like this with a configuration similar to yours, though I removed the overrides:

{
    "eslint.validate": ["javascript", "markdown"]
}

module.exports = {
    plugins: [
    "markdown"
    ],
    extends: [
        "eslint:recommended"
    ],
    env: {
        browser: true
    }
}

In my case, lint rule failures are shown correctly:

But for some reason, syntax errors are all shown on the first line:

It got the column (7) correct, but ignored the line. Running ESLint outside the integration returns the correct line and column:

$ node_modules/.bin/eslint README.md

/Users/brandon/code/eslint/markdown-test/README.md
  5:7  error  Parsing error: Unexpected token !

✖ 1 problem (1 error, 0 warnings)

I don't get any errors in a file that shouldn't have any:

Does this match what you're seeing?

from eslint-plugin-markdown.

Actually now that you mention it yes, that's what I'm seeing but it's not just syntax errors, it's any eslint error.

Here the only error is a style error, spaces after foo

with the space removed

from eslint-plugin-markdown.

😍

from eslint-plugin-markdown.