feat(configuration): add linter.minimumSeverity - #11598
Draft
RodrigoHamuy wants to merge 2 commits into
Draft
RodrigoHamuy wants to merge 2 commits into
RodrigoHamuy wants to merge 2 commits into
Conversation
|
A maintainer will take a look as soon as they can. In the meantime, please make sure that:
|
🦋 Changeset detectedLatest commit: 760e4e2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 13 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Insufficient dataNot enough activity yet to make a reliable assessment. This is an automated analysis by AgentScan |
Adds an option to the linter that raises the severity of every lint rule emitting a diagnostic below the given threshold. It accepts `info` (the default, which preserves the current behavior), `warn` and `error`, and can also be set inside `overrides`. The threshold is applied where the linter already resolves rule severities, so it only affects diagnostics emitted by lint rules. Diagnostics that don't belong to a rule, such as the ones emitted for an outdated configuration schema or for a file Biome can't parse, keep their own severity. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
RodrigoHamuy
force-pushed
the
feat/linter-minimum-severity
branch
from
September 2, 2026 11:57
0779d48 to
bbf476a
Compare
This branch has not been deployed
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
1 participant
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
Follow-up to #7582 (reply in thread), supersedes #11579.
Adds
linter.minimumSeverity(info|warn|error, defaultinfo). Lint rules that would emit below the threshold are raised to it; higher configured severities are kept. Also available inoverrides[].linter.Applied where lint rule severities are already resolved, so it only affects
lint/*diagnostics. Non-rule information diagnostics (schema version mismatch, unparseable files, verbose output) are unaffected — covered by a test.Test Plan
linter_minimum_severity_*tests incrates/biome_cli/tests/commands/lint.rscargo test -p biome_clipassesAI disclosure
This PR was written primarily by Claude Code, reviewed by me.