Skip to content

linter: --allow CLI flag does not properly map alt plugin names #14906

@connorshea

Description

@connorshea

What version of Oxlint are you using?

1.23.0

What command did you run?

oxlint -c .oxlintrc.json --allow='react-hooks/exhaustive-deps'

What does your .oxlintrc.json config file look like?

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "plugins": [
    "react"
  ],
  "categories": {
    "correctness": "off"
  },
  "env": {
    "builtin": true,
    "es2018": true,
    "browser": true,
    "commonjs": true,
    "node": true,
    "shared-node-browser": true
  },
  "ignorePatterns": [
  ],
  "rules": {
    "react-hooks/exhaustive-deps": "warn"
  }
}

What happened?

react-hooks/exhaustive-deps was not allowed to be violated, and still triggered warnings.

This does work fine when I use --allow='react/exhaustive-deps', so it appears that the CLI may not be mapping alt plugin names like it does in the config file?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions