Skip to content
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

Add standard error handling path #12

Open
JD-P opened this issue Feb 20, 2019 · 0 comments
Open

Add standard error handling path #12

JD-P opened this issue Feb 20, 2019 · 0 comments
Assignees
Labels
Long Term Issues that require long term planning and effort to solve Refactor Changes to the code base aimed at paying off technical debt

Comments

@JD-P
Copy link
Owner

JD-P commented Feb 20, 2019

Right now it's unclear to clients (e.g, GreaterWrong) what should be done in response to an error code from the server. It would be helpful if error responses included json payloads with more information such as whether the error is recoverable and what error message should be shown to the user. This could then be used by clients to automatically distinguish between user-recoverable errors and errors which are not recoverable.

@JD-P JD-P self-assigned this Jun 30, 2019
@JD-P JD-P added Long Term Issues that require long term planning and effort to solve Refactor Changes to the code base aimed at paying off technical debt labels Jun 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Long Term Issues that require long term planning and effort to solve Refactor Changes to the code base aimed at paying off technical debt
Projects
None yet
Development

No branches or pull requests

1 participant