Repository navigation
fix(eslint): turn off unicorn/consistent-boolean-name - #246
Merged
Merged
Conversation
Too noisy: flags established React/DOM prop names like open, checked or disabled, and predicate functions like authorize() or matches() that read naturally without a boolean prefix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
commit: |
|
🎉 This PR is included in version 25.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
unicorn/consistent-boolean-namein the base JavaScript ESLint preset — it's too noisy, flagging established React/DOM prop names (open,checked,disabled) and predicate functions (authorize(),matches()) that read naturally without a boolean prefix.Test plan
npm run test:snapshotnpm run test:lintnpm run buildnpm test🤖 Generated with Claude Code