Add handling of different log levels for messages from Elm #221
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
|
Any updates on getting this in? would help clean our precommit output |
|
Would also like to ping on this, can I help move this forward in any way? |
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.
This PR adds filtering for which Elm log messages actually get to the console, as well as a CLI option (
-q) to control the verbosity level. Though there are three log levels, I kept it to just a binary toggle to keep things simple; I'm happy to take suggestions on that or anything else.Closes #216, more or less (this does nothing for TS-generated messages, but my main issue, at least, was the many
INFO: Load file ...lines, which can now be suppressed).