Add getLoggerNames and getConfiguredLoggers#76
Open
colonelpanic8 wants to merge 1 commit intohaskell-hvr:masterfrom
Open
Add getLoggerNames and getConfiguredLoggers#76colonelpanic8 wants to merge 1 commit intohaskell-hvr:masterfrom
colonelpanic8 wants to merge 1 commit intohaskell-hvr:masterfrom
Conversation
These functions allow library consumers to enumerate loggers that have been registered in the global hierarchy, which is useful for building introspection tools (e.g. D-Bus interfaces that report active log levels). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
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.
Summary
getLoggerNames :: IO [String]— returns the names of all loggers in the global hierarchygetConfiguredLoggers :: IO [(String, Priority)]— returns names and levels of loggers with an explicitly setPriorityThese functions expose read-only access to the internal
logTree, enabling library consumers to build introspection tools. My use case is a D-Bus interface (dbus-hslogger) that reports which loggers are active and at what level, without requiring the caller to track that state separately.Test plan
cabal test— 6/6)readMVar), no mutation of global state🤖 Generated with Claude Code