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
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:
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: