Better errors

[light hull]

I use the crate eyre (similar to anyhow) to return results from commands.
I use it instead of anyhow because it returns errors with nice backtrace (similar to unwrap) which is useful.
The problem is that eyre (and anyhow) doesn't implement Serialize so I can't propagate errors with ? in tauri commands.

So I created a fork to eyre and implemented serialize for their Report type.
Finally I can propagate almost any error in tauri commands.
But the current implementation use .to_string() and it turns out that their fmt::Display is useless, it doesn't show summarized backtrace, but just the top error string.
if I change a bit the implementation of the serializer to return format!("{:?}", ...) then finally I get meaningful errors in the browser.
But I'm not sure if it's right to return it like that by default, and I'm looking for advices, how do we get into the point where we can easily propagate errors in tauri projects?

[crimson imp]

But I'm not sure if it's right to return it like that by default
Well, that's really up to you... What i did in the past (though only started it and never actually used it) was to serialize the error into an object: https://github.com/FabianLars/mw-toolbox/blob/026ce36768bd52871f9ebd73beb2d24393e086e3/crates/mw-tools/src/error.rs#L80-L81 you can really go nuts here.

If you want to set different levels of verbosity for example for debug vs release builds you could set that level in a global OnceCell and then read that in the serialize fn.

[light hull]

I wish that I could propagate any error from anyhow / eyre without custom forks or without worry about implementing From to any error.
90% from the errors I don't need their type, but just simple error / backtrace (Eyre helps in general projects, just missing serialize currently for tauri and it dosen't implement From anyhow errors :\ )

[crimson imp]

well, you must have something (if the crates don't implement serialize) :/