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
- Move macros to a new test-log-macros crate.
- Export env_logger and tracing_subscriber from the test-log crate.
- Macros emit test_log::{env_logger,tracing_subscriber} references.
Removes the need for users to explicitly depend on additional crates.
Fixes#36.
- Move macros to a new test-log-macros crate.
- Export env_logger and tracing_subscriber from the test-log crate.
- Macros emit test_log::{env_logger,tracing_subscriber} references.
Removes the need for users to explicitly depend on additional crates.
Fixes#36.
See the features section of the README.
I think the usual pattern for this is:
log
andtrace
which are reexported.test-log
to "runtime".trace
andlog
features enable"runtime"/log
and"runtime"/trace
, respectively.test-log
, refer tolog
andtrace
as"runtime"::log
and"runtime"::trace
, respectively.This would produce a nicer user experience.
The text was updated successfully, but these errors were encountered: