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
If I want to use logging for different modules, I would have destinations (like file) depending on the module.
Has it been planned or envisaged to write to a specific logger and not to all managed loggers ?
For example, I would create a console and a file logged for the main part of an application, but also would have a specific logger for a module (let's call it "module"). That would be convenient to have InfoTo(), WarnTo(), etc... for this:
A complete management of different logger sources with associated destinations would be better, but I think it's a good compromise to add such a functionnality without breaking compatibility.
The text was updated successfully, but these errors were encountered:
If I want to use logging for different modules, I would have destinations (like file) depending on the module.
Has it been planned or envisaged to write to a specific logger and not to all managed loggers ?
For example, I would create a console and a file logged for the main part of an application, but also would have a specific logger for a module (let's call it "module"). That would be convenient to have InfoTo(), WarnTo(), etc... for this:
A complete management of different logger sources with associated destinations would be better, but I think it's a good compromise to add such a functionnality without breaking compatibility.
The text was updated successfully, but these errors were encountered: