Translate warn to warning for Elixir >= 1.11.0 #113
Merged
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.
Logger.compare_levels/2 triggers IO.warn/1 whenever we use it with
:warn
as parameter:Sadly, any backend configured for
Logger
will translate:warning
level to:warn
for backward compatibility (ref), which makes the current implementation of this library to always trigger theIO
warn message for warning logs.This PR addresses that by converting the log
:warn
level to:warning
before callingLogger.compare_levels/2
for Elixir>= 1.11.0
.