Add verbosity levels for warnings and errors#3371
Open
tesujimath wants to merge 1 commit into
Open
Conversation
These behave the same as normal in terms of output formatting, but have a minimum log level of warning and error respectively. This is useful when formatting to stdout with e.g. --out /dev/fd/1 to avoid the "<file> was formatted." message appearing in the output.
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.
These behave the same as normal in terms of output formatting, but have a minimum log level of warning and error respectively.
This is useful when formatting to stdout with e.g.
--out /dev/fd/1to avoid the"<file> was formatted."message appearing in the formatted output.
(Being able to format to stdout seems to be essential for e.g. hooking Fantomas into Emacs Aphelia.)
Relates to #2665