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.

Sign up for GitHub

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

Jump to bottom

Enable custom reject implementation to leverage the built-in "code to statusCode" mapping #1942

Open
2 tasks
bajtos opened this issue Oct 30, 2018 · 0 comments
Open
2 tasks

Enable custom reject implementation to leverage the built-in "code to statusCode" mapping #1942

bajtos opened this issue Oct 30, 2018 · 0 comments
Labels
Extensions feature good first issue help wanted

Comments

@bajtos
Copy link
Member

bajtos commented Oct 30, 2018

Users wishing to provide their own implementation of reject action need a way how to decide which HTTP status code to use depending on the error code, e.g. to map error code ENTITY_NOT_FOUND to status code 404.

See also the discussion in #1867

Acceptance criteria

  • A public API allowing custom reject implementations to map error codes to status codes
  • A new subsection in Handling errors explaining how to write a custom reject implementation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Extensions feature good first issue help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bajtos