Order LoggingLevel from least to most severe#7
Open
jhrcek wants to merge 1 commit intoTritlo:masterfrom
Open
Conversation
jhrcek
force-pushed
the
jhrcek/LoggingLevel-Ord
branch
from
c8331a4 to
ad50df4
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hello @Tritlo
thank you for creating this library!
I'd find it useful in my project if I could order the LoggingLevel using Ord instance based on severity.
See https://modelcontextprotocol.io/specification/2025-11-25/server/utilities/logging#log-levels