Allow omitting specific rules from fix

I am aware #208 was already closed, however since then a specific API for filtering rules from being fixed was added to CLIEngine https://eslint.org/docs/developer-guide/nodejs-api#cliengine .

One of the pain points with the solution in #208 is that the no-autofix plugin requires adding it into every project specifically and only supports the builtin rules.

I’d like to propose again supporting an eslint.rulesToDisableWhileFixing option that takes a list of options. The vscode-eslint could then use this list like so:

newOptions.fix = function({ ruleId }) {
  if (!pluginOptions.rulesToDisableWhileFixing) {
    return true;
  }
  return !pluginOptions.rulesToDisableWhileFixing.includes(ruleId);
}

[branflaker]

Another idea for a possible implementation. Instead of specifying rules to disable for autofixing, how about specifying a path to a separate ESLint config? You get a lot more control over how you want your autofixes applied then (more than just disabling specific rules). Something like:

{
  "eslint.options": { "autofixConfigFile": "C:/mydirectory/.eslintrc.json" }
}

[Jamesernator]

Alternatively as an even more flexible option it might be a possibility to treat eslint.options.fix as a function body if it happens to be a string e.g.:

const fix = typeof newOptions.fix === 'string'
  ? new Function('rule', newOptions.fix)
  : newOptions.fix;

Then in settings.json one could do:

{
  "eslint.options": {
    "fix": "return !['prefer-const', '@typescript-eslint/no-unnecessary-type-assertion'].includes(rule.ruleId);"
  }
}

Or maybe just eval the 'fix' option to get a function:

{
  "eslint.options": {
    "fix": "({ ruleId }) => !['prefer-const', '@typescript-eslint/no-unnecessary-type-assertion'].includes(ruleId)'"
  }
}