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
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.
The text was updated successfully, but these errors were encountered:
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 totracing
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 incargo xtask
-like rust scripts than spawning subprocesses, if only for the guarantee that the samewasm-bindgen
version is used across the rust-compilation / binary invocation boundary.The text was updated successfully, but these errors were encountered: