fault icon indicating copy to clipboard operation
fault copied to clipboard

Go errors but structured and composable. Fault provides an extensible yet ergonomic mechanism for wrapping errors.

Results 9 fault issues
Sort by recently updated
recently updated
newest added

If a library uses this fault package but the caller does not (yet) then the reported error line is within the library which is not so useful to the caller....

bug
help wanted
good first issue

It's been about a year that this library has been in production use in multiple real-world revenue-generating products and I've got a good handle on the improvements I want to...

Hi, thanks for the library. While testing the library, I see that `fctx` only supports `string` values. If I want to add a struct to the metadata, I'll have to...

enhancement
good first issue

I'm honestly not super sure how this will work... There was a case where a function iterated through a list of items and performed work that errored. The output error...

A common use-case for Fault is to wrap user-facing errors with fmsg.WithDesc where the second argument is a well-formed sentence of copy intended to be displayed to non-technical end-users. One...

For Go 1.20

enhancement
good first issue

I think there is an advantage to have common error types directly in the fault library so that other libraries can throw a common fault that can be extracted from...

enhancement
question

Currently, Fault has this concept of a wrapper that has a message and a wrapper that is just a wrapper with metadata. The wrappers that only provide metadata and do...

Once API is v1, provide some snippets since I write errctx wrapping constantly: ```json { "if err != nil": { "prefix": "iferr", "body": [ "if err != nil {", "\treturn...