Allow custom errors to specify response HTTP codes #1301
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently if you throw an error during any action, the response code is always 400. This change allows you to use the following pattern:
then in an action:
This will result in a "Invalid userId" message passed back, with a responseHttpCode of 404 (not found). You can define as many error types as you want this way, e.g. using
SessionError/AuthError
for indicating 401/403 responses,ServerError
for 5xx series errors (remote database failed), etc.