This repository has been archived by the owner on Feb 22, 2023. It is now read-only.
Removed get_api_exception and replaced with built in DRF exceptions #974
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.
Fixes
Fixes #843 by @sarayourfriend
Description
In this PR I have done the following: -
get_api_exception
function with the appropriate built-in DRF exception fromrest_framework.exceptions
.try: queryset.get(); except Model.DoesNotExist: ...
pattern, replaced it with get_object_or_404.get_api_exception
function.Testing Instructions
Checklist
Update index.md
).main
) or a parent feature branch.Developer Certificate of Origin
Developer Certificate of Origin