fix: log to stdout using tracing subscriber. #95
Merged
Conversation
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
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.
Fixes #94
Ideally one would be able to specify the log level via command line arguments but I'm not sure it's worth the extra complexity.
Instead of expanding the interface of the CLI by adding a verbosity flag, I thought it made more sense to just hardcode it to something sane: log everything within the crate, only info logs from other crates.
The reason I had to do
info,cooklang=info,cook=traceis because the filter parsing was applyingcook=traceas a regex to all crates starting withcook, including all thecooklangones which we don't really want to log here.