You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when we build up errors we get a longer and longer error when we go up the stack.
Ideally we would have structured errors like the slog logger. This would allow us go enrich the error with new attributes to give context.
The advantage of this would be that when you eventually log the error slog could pick up the attributes. It would also become possible to ask the attribute of the error for error handling.
Its still a rough idea and i post this issue to see how the response would be.
The text was updated successfully, but these errors were encountered:
This isn't a concrete proposal (or any proposal at all). The issue tracker is not the place for general discussions.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
Proposal Details
Currently when we build up errors we get a longer and longer error when we go up the stack.
Ideally we would have structured errors like the slog logger. This would allow us go enrich the error with new attributes to give context.
The advantage of this would be that when you eventually log the error slog could pick up the attributes. It would also become possible to ask the attribute of the error for error handling.
Its still a rough idea and i post this issue to see how the response would be.
The text was updated successfully, but these errors were encountered: