mac/ctrl+s/ Unable to repair itself

Tell us about your environment

• ESLint Version: “eslint”: “^5.16.0”
• VS-code ESLint extension Version: 2.1.8
• Node Version: v10.15.3
• npm Version: 6.4.1 What parser (default, Babel-ESLint, etc.) are you using? ESLint Please show your full configuration:

Configuration

  "eslint.options": {
        //指定vscode的eslint所处理的文件的后缀
        "extensions": [
            ".js",
            ".vue",
            ".ts",
            ".tsx"
        ]
    },
    "editor.codeActionsOnSave": {
        "source.fixAll.eslint": true 
    },

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint. Add a space outside the rule and save

 console.log('1') //Pay attention to the Spaces

// What all not/Auto repair

What did you expect to happen?

Spaces are automatically removed What actually happened? Please include the actual, raw output from ESLint.

When I use the lower version，

Are you willing to submit a pull request to fix this bug? Beyond the ability

[g-plane]

It seems that it’s a problem of ESLint extension from VS Code, not ESLint itself. To confirm this, can you try running ESLint from CLI?

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.