HackSoftware/Django-Styleguide
1
1
Fork 0
mirror of https://github.com/HackSoftware/Django-Styleguide.git synced 2024-11-22 09:36:36 +03:00
Code Issues Packages Projects Releases Wiki Activity

Mention RFC7807 in the Errors & Exception Handling section

Browse Source
This commit is contained in:
Radoslav Georgiev 2023-07-12 15:20:04 +03:00
parent 4e65208844
commit 231773a58b
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -1587,6 +1587,8 @@ That's why we'll split things into two - **general guidelines**, followed by som
1. Use DRF's default exceptions, with very little modifications. 1. Use DRF's default exceptions, with very little modifications.
1. HackSoft's proposed approach. 1. HackSoft's proposed approach.
If you are looking for a standard way to structure your error responses, **check RFC7807** - <https://datatracker.ietf.org/doc/html/rfc7807> (as proposed here - <https://github.com/HackSoftware/Django-Styleguide/issues/133>)
### How exception handling works (in the context of DRF) ### How exception handling works (in the context of DRF)
DRF has an excellent guide on how exceptions are being handled, so make sure to read it first - <https://www.django-rest-framework.org/api-guide/exceptions/> DRF has an excellent guide on how exceptions are being handled, so make sure to read it first - <https://www.django-rest-framework.org/api-guide/exceptions/>