fix: default severity in CLI with partial 'diagnostics.severity' config #2731
Conversation
This file contains 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
tomlau10
force-pushed
the
bugfix/cli_default_severity
branch
from
a329e7e
to
0f64ab1
Compare
carsakiller
requested changes
Jun 26, 2024
tomlau10
force-pushed
the
bugfix/cli_default_severity
branch
from
0f64ab1
to
917bdfe
Compare
carsakiller
approved these changes
Jun 26, 2024
|
Thank you! |
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.
The default severity when running CLI
--checkis incorrectly set to'Warning'if thediagnostics.severityconfig table is incomplete.This will fix #2730 .