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

More descriptive error messages #39

Open
TorrentofShame opened this issue Sep 19, 2021 · 0 comments
Open

More descriptive error messages #39

TorrentofShame opened this issue Sep 19, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@TorrentofShame
Copy link
Contributor

Error messages (ie: 400: Bad Request) should contain messages describing what caused the error (except for sensitive information).

For example, when the client sends an invalid JSON doc, the server should return an error payload like so:

{
    "code": 400,
    "name": "Bad Request",
    "description": "The browser (or proxy) sent an invalid JSON document."
}

The server should also detail what field caused a validation error to occur (ie: sending fields of the incorrect datatype)

@TorrentofShame TorrentofShame added this to the Become Hackathon Ready milestone Sep 19, 2021
@TorrentofShame TorrentofShame added the enhancement New feature or request label Sep 19, 2021
@TorrentofShame TorrentofShame removed this from the Become Hackathon Ready milestone Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant