Plugin does not work with autofix

[tunnckoCore]

ref: AtomLinter/linter-eslint#815

Everything just started with AtomLinter/linter-eslint#779.

I just have a markdown file, javascript file and eslintrc.

I'm using:

% ❯ npm ls | grep eslint                                                                               February 12, 12:34:53
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]

and have this config

{
  "extends": ["standard"],
  "plugins": ["markdown"],
  "rules": {
    "semi": [
      2,
      "always"
    ]
  }
}

Intentionally makes standard to always want semicolons so it is easy to see if autofixing works.

Initially I was thinking it is Linter-ESLint bug, but seems it isn't. Because when run the following ESLint still report errors and does not fix them.

eslint --fix --ext md README.md
eslint --fix --ext md .
eslint --fix -c .eslintrc --ext md README.md

the code fences in the markdown file is both jsx and js

[platinumazure]

Plugins that use processors (that is, plugins which need to extract JavaScript snippets out of non-JavaScript files) are not able to use autofix due to architectural/design limitations we haven't yet been able to overcome. So files linted using eslint-plugin-markdown won't have autofix applied to them.

As you've noted, this is a core ESLint issue and not something restricted to editor integrations.

When I'm on a PC, I'll find the relevant issues and put them in here.

[privatenumber]

@platinumazure Has anything changed to make this easier to add since the release of ESLint v4?

[not-an-aardvark]

No. However, this might be possible soon if eslint/eslint#9090 is merged.

[KaiSchwarz-cnic]

This got merged, so +1

[BridgeAR]

It would be very nice if this could be worked on now.

[byzyk]

Guys, I created PR #97 for this feature. Feel free to share the feedback if it works for your use cases.

[tunnckoCore]

Seems like it works through terminal, but does not writes the fixes?

Also, it does not work in a editor, does we need some option for the eslint extension for VSCode?

Seems like adding to eslint.validate is not respected

{
  "language": "markdown",
  "autoFix": true
}

Some may have Prettier extension for VSCode too, but still it doesn't do all needed things. So, for me currently, this problem above isn't so much of a big deal.