Skip to content

Figure out the right set of cases in error #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lukewagner opened this issue Mar 4, 2023 · 0 comments
Open

Figure out the right set of cases in error #5

lukewagner opened this issue Mar 4, 2023 · 0 comments

Comments

@lukewagner
Copy link
Member

Spinning out from this comment, we should discuss what the right set of variant cases are for error. Ideally, we'd be able to align with something in the HTTP spec, but I'm not sure what that is (noting that the well-defined status codes are already in a separate status-code field in responses).

As a general principle, I think it's a good idea to have separate cases only when code might want to actually branch and handle the different cases differently; to convey extra information for debugging purposes we can use the case payloads (e.g., with a string).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant