Comments (2)
There is probably a law that states that any open source Rust project will eventually be asked for serde support.
Anyway, to have this would be great (maybe behind a feature flag, as is tradition).
The use case for me is that I have a networked library, and I want to propagate something like
Report
back to the client, to have more meaningful errors on the client.
I'd be happy to merge serde support but I'm worried that we would be fairly limited in what support we could implement and that it might not be what you have in mind. color-eyre
only provides a hook for eyre
, which itself stores errors as type erased trait objects. We can't accurately serialize the source error beyond converting it into a chain of messages that we reconstruct as a different type on the other side. We could serialize the content of the EyreHandler
that color-eyre
provides, and a limited version of the dyn Error
which is recreated lossily on the other side and hidden inside of the Report
, but that's pretty much the limit. Also it wouldn't be a serialization impl directly on the eyre::Report
, it would instead have to be a fallible adapter that attempts to access the handler, and if the handler is the one exported by color-eyre
it grabs that context, and the error and wraps them in a type that implements Serialize
.
If you're still interested in this I can help describe how to implement it but otherwise I don't expect I'll be able to make time to implement this support myself in the near term.
from color-eyre.
Duplicate of #77 (kinda)
from color-eyre.
Related Issues (20)
- Outdated documentation about color-backtrace
- How to access fields of a Report
- Attach Report's to an error via Section::error()
- Report creation takes a lock HOT 3
- Print a backtrace/spantrace to debug logs not to stderr HOT 1
- panic in tests (I used master) HOT 1
- Is there an easy way to make custom errors have equivalent report functions HOT 1
- show sections when panic macro is called HOT 1
- Output has few/no colors in Gnome Terminal
- should info! events be captured and printed as part of the SpanTrace? HOT 1
- Mechanism to add sections in hook callback
- Omit numbering of errors if there's only one HOT 2
- color-eyre uses the same inexplicable information order as standard backtraces HOT 1
- Automate synchronization between docs.rs and README.md
- Disable setting panic hook HOT 2
- Ergonomics: Full re-exports from `eyre`; export `color_eyre::eyre!` macro, rather than `eyre` crate HOT 2
- Add a config option to print panic output to stdout.
- First eyre::Result::Err variant is slow to construct if backtraces are enabled
- Construct a new `Handler` after already having created one / modify handler HOT 1
- Wrap types so we don't have to re-export `owo_colors` HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from color-eyre.