-
Notifications
You must be signed in to change notification settings - Fork 136
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
Formalize errors, esp. client vs. server #73
Labels
Milestone
Comments
Getting tackled in the currently ongoing v2 redesign! Issue: #143 / PR: #145 |
27 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should formalize the errors we throw (e.g. in cases where we have custom messages, like connection errors, or "node doesn't exist", etc.), but most importantly, there should be a documented way to determine whether a thrown error is due to a client mistake (e.g. "node doesn't exist") vs. a server one (e.g. connection error). This generally maps pretty nicely to HTTP 4xx vs. 5xx status codes.
The text was updated successfully, but these errors were encountered: