Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 useExhaustiveDependencies' option hooks config schema is incorrect #2396

Closed
1 task done
afonsojramos opened this issue Apr 10, 2024 · 0 comments · Fixed by #2401
Closed
1 task done

🐛 useExhaustiveDependencies' option hooks config schema is incorrect #2396

afonsojramos opened this issue Apr 10, 2024 · 0 comments · Fixed by #2401
Assignees
Labels
A-Analyzer Area: analyzer S-Bug-confirmed Status: report has been confirmed as a valid bug

Comments

@afonsojramos
Copy link
Contributor

Environment information

CLI:
  Version:                      1.6.4
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.10.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/8.10.5"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 false

Workspace:
  Open Documents:               0

What happened?

image

And looking at the schema itself, it seems that it is indeed correct.
image

But this goes against the documentation, and the matter of the fact is that setting it to true actually works.

Expected result

No error should show.

Code of Conduct

  • I agree to follow Biome's Code of Conduct
@afonsojramos afonsojramos changed the title 🐛 useExhaustiveDependencies config schema is incorrect 🐛 useExhaustiveDependencies' option hooks config schema is incorrect Apr 10, 2024
@arendjr arendjr added S-Bug-confirmed Status: report has been confirmed as a valid bug A-Analyzer Area: analyzer labels Apr 10, 2024
@arendjr arendjr self-assigned this Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Analyzer Area: analyzer S-Bug-confirmed Status: report has been confirmed as a valid bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants