Luke Frisken
Luke Frisken
This idea doesn't fit with the current model of LanguageLoader, having a "current language" because it could change with every request and you would want all language resources to be...
I think the WIP pull request #62 is supposed to address this
I also hit this, and had to rework some code. I'm guessing the error types need to own the path and that's why this is done?
the readme mentions a `composeL!` macro, but does this actually exist or is it expected to implement this yourself?
I'm looking at a way to send tracing data between Rust processes via a serde bridge, this would be very useful. Will probably end up implementing a stripped down proof...
Okay so I got most of the way through the implementation of this feature but was blocked on trying to create a value set with `tracing_core::field::value_set()`, being very difficult, perhaps...
@Ekleog it's not perfect due to lifetime issues I ran into, but here's what I've got so far https://github.com/AleoHQ/tracing-bridge I'm also using it between a rust executable and a rust...
@Ekleog yes it's not perfect, it seems like the API methods available don't allow this to be done properly with tracing. I just tried to hash together something as well...
This would also allow working around any shortcomings in the short term that the derive may have in terms of schema expressability with attributes, without having to implement the entire...
Same with IntoParams attributes