Feature request: `noInlineConfig` flag

[webbertakken]

Trying to keep some projects clean by not allowing inline disables in favour of proper configuration of fitting rules for the project. I'm liking it in my ESLint config and would like to apply it to Oxlint as well before migrating.

In ESLint the following configuration can be used to not allow inline comments:

  {
    linterOptions: {
      noInlineConfig: true, // ignores all /* eslint-disable */ etc.
      reportUnusedDisableDirectives: 'error',
    },
  }

For Oxlint the best we have (that I could find) is

  // Base rules
  "rules": {
    "unicorn/no-abusive-eslint-disable": "error"
  },

We also have

# report unused rules as warnings
oxlint --report-unused-disable-directives

# report unused as errors
oxlint --report-unused-disable-directives-severity=error

But there is currently no way to disallow inline config completely for a project.

It would be really nice if we could have noInlineConfig setting or rule for Oxlint.

Considered alternatives

We could probably do this with a custom rule

[kwangure]

I'm wondering how to configure --report-unused-disable-directives and --report-unused-disable-directives-severity=error in .oxlintrc.json instead of CLI so that it works for VS Code as well. Is this supported?

[webbertakken]

@kwangure You can use "oxc.unusedDisableDirectives" in VS Code

See https://marketplace.visualstudio.com/items?itemName=oxc.oxc-vscode#:~:text=oxc.unusedDisableDirectives

[kwangure]

Just what I needed! I didn't think to check there. Maybe there should be a VS Code page on the OXC site with these.

Also, it feels like some of these VS Code settings/CLI args should also be options in .oxlintrc.json where they're applied to both the LSP and via CLI.

Anyway. This is sufficient for now. Thanks Webber!

[connorshea]

I like the idea of a webpage for the VSCode extension, you should open an issue about that