This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
enhancement: Add quiet flag to hide warnings #4025
Merged
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.
Sometimes you may want to run linting but ignore any warnings produced, such as in a CI environment where you only want lint failures to fail the build (many runners will check both the exit code and STDERR to see if the program has passed).
This mimics the
quiet
flag available in ESLint, which hides errors from output when passed.PR checklist
Overview of change:
Adds a new CLI flag,
quiet
, to allow hiding of lint warnings.Is there anything you'd like reviewers to focus on?
What's the best way to test this? I've been having trouble trying to do it in the
linterTests
. I've been trying:But that doesn't seem to produce any warnings or errors. Any idea why?
CHANGELOG.md entry:
enhancement: added
quiet
flag to allow hiding of lint warnings