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
We'd like to support the use case of customizing the logger for the WebClient instances that the Bolt App creates. Some of the motivation and ideas around this change were discussed and agreed upon here: #278 (comment)
Side note: in the end we'd like to accomplish the following
logLevel affects the App instance but also cascades to all owned objects with loggers.
to customize the Receiver’s logger, you’re expected to set the receiver option to a fully initialized receiver with your custom logger already set.
to customize the WebClient’s logger, you’re expected to set the clientOptions.logger option (that's what this issue is about).
to customize the App’s logger, use the logger option.
We should probably have tests that verify all the cases above ☝️
Requirements (place an x in each of the [ ])
I've read and understood the Contributing guidelines and have done my best effort to follow them.
Description
We'd like to support the use case of customizing the logger for the
WebClient
instances that the BoltApp
creates. Some of the motivation and ideas around this change were discussed and agreed upon here: #278 (comment)Side note: in the end we'd like to accomplish the following
logLevel
affects theApp
instance but also cascades to all owned objects with loggers.Receiver
’slogger
, you’re expected to set thereceiver
option to a fully initialized receiver with your custom logger already set.WebClient
’slogger
, you’re expected to set theclientOptions.logger
option (that's what this issue is about).App
’slogger
, use thelogger
option.We should probably have tests that verify all the cases above ☝️
Requirements (place an
x
in each of the[ ]
)The text was updated successfully, but these errors were encountered: