Breaks with eslint-plugin-markdown

[heygrady]

https://github.com/eslint/eslint-plugin-markdown

Parsed some markdown files and totally mangled them. Easy to turn off the rule for markdown but other rules (like import/order) seemed to manage the individual code blocks well.

[lydell]

Hi! I've never used eslint-plugin-markdown before. Can you show me how you set things up? The best thing would be a small reproduction repo.

[heygrady]

module.exports = {
  extends: [],
  plugins: [
    'simple-import-sort',
    'markdown',
  ],
  rules: {
    'simple-import-sort/sort': 'error',
  },
  overrides: [
    {
      files: ['**/*.md'],
      parserOptions: {
        ecmaFeatures: {
          impliedStrict: true,
        },
      },
      rules: {
        'simple-import-sort/sort': 'error',
      },
    },
  ],
}

Some text

\\```js
import b from 'b'
import a from 'a'
\\```

[lydell]

Couldn’t you have bothered to post something that actually works? 😢

Anyway, after fighting ESLint’s configuration for a while I finally made it work and could reproduce the issue. But now I lost my steam for working on the bug.

Some text

```js
import b from 'b'
import a from 'a'
```

is autofixed to:

import a from 'a'
import b from 'b'
```

In other words, everything before the first import seems to be removed.

[lydell]

Discovery: The issue only seems to occur when the autofix applies from the very beginning of the code block (index 0).

For example:

Some text

```js
;import b from 'b'
import a from 'a'
```

successfully autofixes to:

Some text

```js
;import a from 'a'
import b from 'b'
```

Feels like a bug in eslint-plugin-markdown. I need to investigate further.

[lydell]

eslint/markdown#119 has been merged, so the next version of eslint-plugin-markdown should not cause removals of markdown above imports anymore.

You might still run into eslint/markdown#120, though.

[lydell]

v1.0.1 of eslint-plugin-markdown has been released! All the above issues should be fixed.

I have some uncommitted test that I need to finish up, then we can close this issue.