Skip Menu |

This queue is for tickets about the Log-Any-Adapter CPAN distribution.

Maintainer(s)' notes

DO NOT FILE TICKETS HERE

This distribution has been merged with Log-Any. Instead, file tickets on Github here → Log Any Issues.

Report information
The Basics
Id: 64479
Status: resolved
Priority: 0/
Queue: Log-Any-Adapter

People
Owner: Nobody in particular
Requestors: sscaffidi [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: feature request: a set_level() method
I'd be happy to contribute the code myself for this - I'll even accept co-maint and do the release work if it makes the decision easier! Basically, I feel that since Log::Any adaptors are already more or less aware of logging levels, the interface for Log::Any should also specify a standard method for setting the log level (which the adaptors would then implement) Let me know what you think, especially if there's a good reason to *not* do so!
On Tue Jan 04 18:21:19 2011, SSCAFFIDI wrote: Show quoted text
> I'd be happy to contribute the code myself for this - I'll even accept > Let me know what you think, especially if there's a good reason to > *not* do so!
I've taken over maintenance and am going over all the RT tickets. I think the Log::API design is that log producers need to do the level check themselves. If you mean that there should be an API to tell Adapters (the log message consumers) to change the level on the loggers they manage, that might be feasible, but that would need to be a change to Log-Any-Adapter, not Log-Any. It also isn't backwards compatible -- existing Adapters won't support it, so there's a migration issue. That said, I'm going to move this ticket to the Log-Any-Adapter queue and if you're still interested, we could discuss design ideas further.