CategoryLogger, all methods accept a message or LogData (allowing for custom data to be passed along, useful for custom loggers e.g.).
In addition all methods accept a lambda returning a message (string) or LogData, the latter is useful if you have rather expensive
calculations to do before you can log it - the lambda will only be called when needed.
All methods ending with a c (e.g. debugc), are deprecated and will be removed in 0.6.0, use the normal ones instead.
This is a special opinionated way to log, that an exception (Error)
occurred, but your code dealt with it in a proper way. That way
we can say, there was an Error/Exception but we resolved it.
This will be logged as: Error (resolved) in the log.
Since 0.5.0, will be removed in 0.6.0, use resolved instead.
This is a special opinionated way to log, that an exception (Error)
occurred, but your code dealt with it in a proper way. That way
we can say, there was an Error/Exception but we resolved it.
This will be logged as: Error (resolved) in the log.
CategoryLogger, all methods accept a message or LogData (allowing for custom data to be passed along, useful for custom loggers e.g.). In addition all methods accept a lambda returning a message (string) or LogData, the latter is useful if you have rather expensive calculations to do before you can log it - the lambda will only be called when needed.
All methods ending with a c (e.g. debugc), are deprecated and will be removed in 0.6.0, use the normal ones instead.