We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tracing-macros
Hey there! Are there any plans to publish tracing_macros
In Ratatui docs, we're suggesting that users create a macro similar to the dbg! macro defined in https://github.com/tokio-rs/tracing/blob/master/tracing-macros/src/lib.rs. The person writing our docs for this suggested using trace_dbg! for the macro name instead of overriding the existing dbg! macro, but I can see the argument either way. It would be nice to have this macro available as something that can be included directly rather than written in each user's app for this however.
dbg!
trace_dbg!
Actually publish https://crates.io/crates/tracing_macros with the macros defined.
From https://discord.com/channels/500028886025895936/974721015999516672/1224430040423334049
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Feature Request
Crates
tracing-macros
Motivation
Hey there! Are there any plans to publish tracing_macros
In Ratatui docs, we're suggesting that users create a macro similar to the
dbg!
macro defined in https://github.com/tokio-rs/tracing/blob/master/tracing-macros/src/lib.rs. The person writing our docs for this suggested usingtrace_dbg!
for the macro name instead of overriding the existingdbg!
macro, but I can see the argument either way. It would be nice to have this macro available as something that can be included directly rather than written in each user's app for this however.Proposal
Actually publish https://crates.io/crates/tracing_macros with the macros defined.
Alternatives
From https://discord.com/channels/500028886025895936/974721015999516672/1224430040423334049
The text was updated successfully, but these errors were encountered: