Clears everything, any registered (root)categories and loggers are discarded. Resets to default configuration.
Return a CategoryLogger for given ROOT category (thus has no parent). You can only retrieve loggers for their root, when logging you specify to log for what (child)categories.
Category root (has no parent)
Return RuntimeSettings to retrieve information about RuntimeSettings for categories.
Set new configuration settings for a category (and possibly its child categories)
Config
Category
True to apply to child categories, defaults to false.
Defaults to false. If set to true and if category is a root category it will reset the root logger.
Set the default configuration. New root loggers created get this applied. If you want to reset all current loggers to have this applied as well, pass in reset=true (the default is false). All categories runtimesettings will be reset then as well.
The new default configuration
If true, will reset all runtimesettings for all loggers/categories to these.
Generated using TypeDoc
Categorized service for logging, where logging is bound to categories which can log horizontally through specific application logic (services, group(s) of components etc). For the standard way of logging like most frameworks do these days, use LFService instead. If you want fine grained control to divide sections of your application in logical units to enable/disable logging for, this is the service you want to use instead. Also for this type a browser plugin will be available.