[LOG4J2-2872] Normalizes level names #815
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
garydgregory
reviewed
Apr 7, 2022
garydgregory
reviewed
Apr 7, 2022
ppkarwasz
force-pushed
the
custom-level-capitalization
branch
from
db37ff2 to
66c843c
Compare
Calling `Level.forName` with a non upper case argument, can create a custom level that can not be retrieved using `Level.toLevel`. This PR fixes to upper case the keys in the `Level.LEVELS` map.
ppkarwasz
force-pushed
the
custom-level-capitalization
branch
from
66c843c to
c275a78
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Calling
Level.forNamewith a non upper case argument, can create a custom level that can not be retrieved usingLevel.toLevel.This PR fixes to upper case the keys in the
Level.LEVELSmap.