Currently, messages such as decode failures are printed directly to Console.Error. This is really helpful for debugging, but isn't very pretty for the users of the CLI. For nuget package users, this results in very verbose logs in all situations.
Consider a way to enable or disable that kind of output.
One such way of handling this would be allowing library classes in this project to take ILogger<T> objects for logging, which would enable the caller to set log level.
This is split off of #103
Acceptance Criteria
[x] Debug-style decode failure messages can be enabled/disabled for output on the CLI
Description
Currently, messages such as decode failures are printed directly to
Console.Error. This is really helpful for debugging, but isn't very pretty for the users of the CLI. For nuget package users, this results in very verbose logs in all situations.Consider a way to enable or disable that kind of output.
One such way of handling this would be allowing library classes in this project to take
ILogger<T>objects for logging, which would enable the caller to set log level.This is split off of #103
Acceptance Criteria