4 ms·
Honestly I don't think Diesel error messages are too bad, they're just extremely verbose to a fault. It'd be nice if it could filter out a lot of the duplicate
by drbawb 8y ago
Honestly I don't think Diesel error messages are too bad, they're just extremely verbose to a fault. It'd be nice if it could filter out a lot of the duplicate information, or maybe just print spans. Usually when I get a Diesel error message it's of the form: "got <this huge tuple of types>, expected <this huge tuple of types with one of them transposed>." If diesel (or the compiler) could just put a span under the element(s) of a generic tuple that don't match it'd help immensely w/ the vast majority of errors I see from that crate.
- inferiorhuman 8y agoWhat caught me off guard were the error messages when not enabling serde functionality for optional dependent crates (e.g. chrono). Nom, which I love, has been a matter of interpreting the error messages with a divining rod though. Emphasizing which part of the tuple didn't match up would be a big win, but IMO it should be pulled out and mentioned first. Highlighting could get lost in the noise (moreso without all the ANSI escape codes if you're redirecting output or whatnot).
- ay 8y ago+1 on needing to specify “serde” as a feature for chrono. Another one was needing to enable “huge-tables” for diesel itself - some of my tables from the “legacy” system have many fields.
- inferiorhuman 8y agoNot just chrono but bigdecimal too (diesel really needs some more explicit documentation IMO).