Vetur Ignores .eslintrc settings when formatOnSave is true

• [ x ] I have searched through existing issues
• [ x ] I have read through docs
• [ x ] I have read FAQ

Info

• Platform: Linux (Ubuntu 16.04)
• Vetur version: 0.11.7
• VS Code version: 1.22.2
• ESLint extension version: 1.4.8

Problem

When "editor.formatOnSave" is set to true in the VS Code settings, Vetur does not respect the settings in .eslintrc.

Reproducible Case

1. Install Vetur VS Code Extension
2. Install ESLint VS Code Extension
3. Add the following to VS Code User Settings:

  "editor.formatOnSave": true,
  "eslint.validate": [
      "javascript",
      "javascriptreact",
      "vue"
  ],
  "eslint.autoFixOnSave": true,
}

1. Reload VS Code
2. Use the vue 3.0 cli (I used version 3.0.0-beta.6) to create a new project: vue create new-project
3. Choose Manually select features
4. Choose Linter / Formatter
5. Choose ESLint + Airbnb config
6. Choose Lint on save
7. Choose In dedicated config files
8. Open the new project in VS Code
9. Make a change to the App.vue file
10. *Notice that it changed single quotes to double and removed trailing commas contrary to the .eslintrc config

[jeffhube]

I solved this by adding the following to the default value for vetur.format.defaultFormatterOptions

"prettier": {
    "singleQuote": true,
    "trailingComma": "all"
}

So it looks like this:

"vetur.format.defaultFormatterOptions": {
    "js-beautify-html": {
        "wrap_attributes": "force-expand-multiline",
    },
    "prettyhtml": {
        "printWidth": 100,
        "singleQuote": false,
        "wrapAttributes": false,
        "sortAttributes": false
    },
    "prettier": {
        "singleQuote": true,
        "trailingComma": "all"
    }
}

[jmcooper]

Looks like I found a config to get this working. If I add the below configuration to VS Code it works although it seems a little glitchy. For example, if in addition to the config below, I also set "editor.formatOnSave": true, then I see the code flash with double quotes and then get correctly formatted with single quotes, so it seems like Vetur might be formatting it with quotes and then ESLint is fixing it afterwards. It would be good if whatever Vetur is doing would respect the .eslintrc config.

Here’s the VSCode config that makes it work:

{
    "eslint.validate": [
        {
            "language": "vue",
            "autoFix": true
        },
        {
            "language": "javascript",
            "autoFix": true
        },
    ],
    "eslint.autoFixOnSave": true,
}