Ergonomic Error Wrapping Techniques in Production Apps
is there an ergonomic way to wrap errors? currently I'm creating a custom error class that extends Data.TaggedError and just adding the returned error as a field in the class. i'm curious how others are doing this in their production apps