Change logger max level to be set by feature #429
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
|
Thanks for the PR! |
Removed `log::set_max_level(log::LevelFilter::Info);`
GabrielMajeri
changed the title
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.
Resolves #428
By changing
log::set_max_level(log::LevelFilter::Info);tolog::set_max_level(log::STATIC_MAX_LEVEL);, the max log level can be set by specifying features.For example, to use info for release and trace for debugging, set
features = ["release_max_level_info", "max_level_trace"].Tested this to work, thought I could just remove that line, but it seems you need to explicitly set it to STATIC_MAX_LEVEL, which is set depending on the features and whether it is a release build.