josiahwitt / erk Goto Github PK

Now that we have errorStack, this additional information could be helpful. Just don't want to confuse the distinction between erk errors and regular errors. Maybe just set type for non-erk errors? 🤷‍♂️

Maybe if there's a newline in a wrapped error message we should prefix the newline with a tab if we're printing it in the message template?

When wrapping an erk error, the original err field is overwritten with the first Erk error. Promote the original err to rootErr, so the original error is not lost.

Currently erk.Kind is an empty interface, meaning we get no type checking. Let's add a method to that interface, which would be implemented on erk.DefaultKind. That switch would require creating kinds like (and would be a breaking change):

type ErkMyKind struct { erk.DefaultKind }

Using struct embedding is useful for other things, like HTTP statuses, or any other metadata you want to attach to the kind (like marking certain kinds as warnings).