`editor.formatOnSave` conflict with `eslint.autoFixOnSave`

two action result in different result, caused by prettier does not respect eslint config . CMT + SHIFT+ P -> Format Document -> Prettier formats code. Save again -> eslint autofix formats code.

// Place your settings in this file to overwrite the default settings
{
    "window.zoomLevel": 1,
    "gitlens.advanced.messages": {
        "suppressCommitHasNoPreviousCommitWarning": false,
        "suppressCommitNotFoundWarning": false,
        "suppressFileNotUnderSourceControlWarning": false,
        "suppressGitVersionWarning": false,
        "suppressLineUncommittedWarning": false,
        "suppressNoRepositoryWarning": false,
        "suppressUpdateNotice": true,
        "suppressWelcomeNotice": false
    },
    "prettier.eslintIntegration": true,
    "prettier.stylelintIntegration": true,
    "editor.formatOnSave": false,
    "eslint.autoFixOnSave": true,
    "eslint.validate": [
        "javascript",
        "javascriptreact",
        {
            "language": "vue",
            "autoFix": true
        },
        {
            "language": "html",
            "autoFix": true
        },
        "vue"
    ]
}

[azz]

It doesn’t make sense to use both at once, as both will run the code through ESLint. You shoud either use:

    "editor.formatOnSave": false,
    "eslint.autoFixOnSave": true,

or

    "editor.formatOnSave": true,
    "eslint.autoFixOnSave": false,

[tiptopcoder]

For the latest eslint extension, the settings should look like this:

{
  "editor.formatOnSave": false,
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  }
}