Honor Logger#level overrides #41
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.
We attempt to override
Logger#levelin Rails’s Logger subclass to allow setting a different level per thread (and thus per request). ButLogger#addchecks the new message’s severity against the@levelinstance variable, so overriding#leveldoesn’t have the intended effect. (We also prepend a check against#levelto#add, so you can only set the thread-local level greater than or equal to@level, not less. We’d like to allow setting any thread-local level.)This patch modifies
Logger#addto check#levelso that third-party loggers can customize how the current level is determined without needing to reimplement#addor juggle multiple underlying Logger instances.