You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have started this week to play with the Log::Any context data and structured data feature. With respect to the context data feature I was misled by the object method based access: $log->context. I thought the context belongs to the logger and maybe to subloggers, if we take logger category namespace inheritance into consideration. But if I have understood it right now the context is a property of the Log::Any::Manager singleton instance. From my perspective the following class method should be added to Log::Any
sub get_context { $manager->get_context }
If this sounds reasonable I can create a PR.
The text was updated successfully, but these errors were encountered:
XSven
changed the title
[feature] non-static (object based) access of context data is misleading
[feature] non-static (object based) access of context data is sometimes misleading
Nov 11, 2022
Unfortunately, the context is global because the proxy objects don't have any kind of parent/child relationship, and trying to infer one based on categories would be impossible. Having a plain Log::Any->context accessor would probably be fine: It aligns with my desire to get rid of the Manager class entirely and move all its functionality into the base Log::Any class.
I have started this week to play with the Log::Any context data and structured data feature. With respect to the context data feature I was misled by the object method based access:
$log->context
. I thought the context belongs to the logger and maybe to subloggers, if we take logger category namespace inheritance into consideration. But if I have understood it right now the context is a property of the Log::Any::Manager singleton instance. From my perspective the following class method should be added to Log::Anysub get_context { $manager->get_context }
If this sounds reasonable I can create a PR.
The text was updated successfully, but these errors were encountered: