This repository was archived by the owner on Feb 9, 2023. It is now read-only.
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.
Description
This pull request adds a custom exception handler to the Django project. The handler provides a consistent way of handling exceptions and gives better control over the handling process. If an exception is not handled, the handler will now return a 500 response code without any garbage-like error messages.
Related Issue
#109
Motivation and Context
I did not observe 500 code as mentioned in the issue, however, it would be appropriate to have an exception handler. While we currently only raise Validation Errors in the codebase, it is possible that we will need to add custom errors in the future. Having a handler in place will allow us to customize the error messages and response codes for these errors.
Screenshots (if appropriate):