Possible to _not_ use a default stdout logger? #104
Closed
JensMertelmeyer
started this conversation in
Ideas
Replies: 1 comment
-
|
I think this should be a change in spdlog-rs so I created an issue #105 to track it. Thanks for opening this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We use
spdlogheavily throughout our application. However, runningcargo testwill flood the console with logs because in several hundred tests, we were too lazy to set up a separate mock logging instance and it will all go to spdlog's default stdout/stderr logger.I have not been able to find a way around it. While spdlog's creation of a default logger (if none has been set up yet) is a beautiful feature, it's not quite what we need within our tests.
Would it be possible to put this behind a feature flag? Or is there some other way of controlling (possibly from
Cargo.tomlwhat the default logger should be (like chosing between a "null" logger or regular stdout/stderr)?Beta Was this translation helpful? Give feedback.
All reactions