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
Module-related code that needs to use logging facilities is increasingly located in free functions which don't have the Module instance in scope, and manually saving the instance as a self variable just to use logging functionality feels weird and self-referential. Instead let's just have module files create their own TBLog instances and call log functions on those.
Once this is done we can remove the cheeky Object.assign() bits of logging-related code which set the logging methods on modules, and also the bit that causes the exported TBLog function to also work as a "default logger" with no caller (since everyone creating their own logger instances will always specify a caller).
Module-related code that needs to use logging facilities is increasingly located in free functions which don't have the
Module
instance in scope, and manually saving the instance as aself
variable just to use logging functionality feels weird and self-referential. Instead let's just have module files create their ownTBLog
instances and call log functions on those.Once this is done we can remove the cheeky
Object.assign()
bits of logging-related code which set the logging methods on modules, and also the bit that causes the exportedTBLog
function to also work as a "default logger" with no caller (since everyone creating their own logger instances will always specify a caller).Related to 9519582
The text was updated successfully, but these errors were encountered: