Barnaby Keene

the `msg=` component is typically the human readable entry, no need for multiple, i've never seen any software do two independent log entries

Hey Leigh, sorry for the late response! Yeah, case 1-c is what I'm seeing as the bug here. omitempty is useful for avoiding this and we've done that in a...

Absolutely love this suggestion, I've already added an issue to start implementing it into the backend so server owners can declare whether or not their server has a custom IMG...

I've already planned to have a `required` declaration for each file.

0.3.8/-DL offered some nice features but I still think this sort of download feature would be cool as it would allow more complex modifications such as complete replacements, audio files,...

Potential solutions: Assume that any .Error() strings that are just matching the pattern `^$` are to be ignored. - Pros: simple - Cons: if anyone else wants to implement Fault...

Yeah I think you're right here, I went back and forth quite a bit on stack trace implementation and eventually settled on something quite simple though it's unfortunately opinionated. I...

This makes sense, Fault is designed as an error library library - a toolkit for building our your error handling solution with your own wrappers to chain in .Wrap calls...

Yeah this is being worked on, I'll get a PR open for feedback from users soon! I also do a similar thing with sentinel errors so there's a lot of...

It might be impossible, it might just be a case of the user needing to write the multierr handler code in their error handling procedure which, given the error chain...