Replies: 2 comments
-
You won't get the benefit of logging with context, and your components will be less reusable independently. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for the information!
And just to be sure then: the way to pass a log object is to pass the log
object to all model instances directly, yes? Is there an easy/convenient
way to do that -- with a helper, perhaps?
…On Mon, Aug 28, 2023, 6:23 PM Sebastian Riedel ***@***.***> wrote:
You won't get the benefit of logging with context, and your components
will be less reusable independently.
—
Reply to this email directly, view it on GitHub
<#2098 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD6K6SFTAAUBIXV6ZOLX4DXXUR7RANCNFSM6AAAAAA4CCD7VU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Would there be anything wrong with a Mojo::Log singleton pattern to access a single shared Mojo::Log object from everywhere inside the process?
It's a bit annoying to pass the application log object to all model objects, and I want all model objects to write to the same custom log location as the application is configured for. Moreover, when capturing logs in tests, it'd be nice to just capture on the one instance.
Beta Was this translation helpful? Give feedback.
All reactions