Skip to content
New issue

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

[enhancement] Use tracing instead of log #424

Open
ActuallyHappening opened this issue Jan 23, 2025 · 1 comment
Open

[enhancement] Use tracing instead of log #424

ActuallyHappening opened this issue Jan 23, 2025 · 1 comment

Comments

@ActuallyHappening
Copy link

I am consuming the library version of cargo-leptos (with a few patches ofc) and logs coming from the library don't have a target. Porting to tracing should be transparent to users, but allow for library users like me to benefit from all of tracings features. Admittedly not many people are using this as a library, but it is much cleaner in cargo xtask-like rust scripts than spawning subprocesses, if only for the guarantee that the same wasm-bindgen version is used across the rust-compilation / binary invocation boundary.

@ActuallyHappening
Copy link
Author

OK I'm going to work on a PR to this effect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant