Add log_level option to logger default formatter #1079
Merged
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
iMacTia
approved these changes
Dec 27, 2019
|
awesome! thank you 👍 |
dgholz
added a commit
to dgholz/oauth2
that referenced
this pull request
Jan 24, 2020
lostisland/faraday#1079 changed the logging to all use the same level, and it defaults to `:info`. This changed the log level used for request and response headers and bodies. I changed the specs to expect the logs from Faraday to be INFO-level
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.
Description
Logger default formatter log severity can now be configured through the
log_leveloption (related #1078)Todos
List any remaining work that needs to be done, i.e: