Use DRF handlers for 400 and 500 status codes#21
Draft
tomneep wants to merge 1 commit intoCLIMB-TRE:mainfrom
Draft
Use DRF handlers for 400 and 500 status codes#21tomneep wants to merge 1 commit intoCLIMB-TRE:mainfrom
tomneep wants to merge 1 commit intoCLIMB-TRE:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Uses DRFs generic error views for status codes 400 and 500. I'm not really sure how to test this in CI but I can run locally and use curl to hit a badly configured server.
Without this I get
with this I get
{"error": "Server Error (500)"}which for an API seems more appropriate (hopefully we aren't getting these errors though!)