Code a sample view which uses permissions derived from BaseProblemPermission class and throws a registered exception. Write tests with this view to test the following behaviors:

• When the permission passes, content type is "application/json".
• When the permission fails, content type is "application/problem+json" and the problem code is the same as the one declared in the registered exception with the permission.

Write tests for the ErrorDocumentationView for both behaviors:

• Using a registered problem code, response has content type "application/json" and the data is documented correctly.
• Using an invalid problem code, response has content type "application/problem+json" and the status is 404.

Using mixins are needlessly ugly for very customized views. Decorators would be a nice way.

https://stackoverflow.com/a/38407227

The setting necessary for the "problem description url" is explained here https://github.com/shivanshs9/drf-problems/#installation .

And if I follow those directions I get a error url in the returned JSON ...

... but I don't understand how to take this further. How can I control what the url is for a given situation ? Any further explanation would be appreciated. Thanks.

Solution is to remove the six dependency and migrate fully to using python 3. Tested with Django 4.1 and python 3.10

The latest release is not working with Django 4 due to 65dcccf

Would it be possible to release a version including the fix above?

If there is a serializer data validation error on a field title, status or type, the validation message will be overwritten by drf-problems which forces exception meta info into those fields.

The rfc defines an instance attribute too to my understanding : https://www.rfc-editor.org/rfc/rfc7807#section-3.1

How do I add it to the exceptions?

Looking at the code doesn't seem to be defined?

Is there a way to add custom attributes?

Write tests with a sample view to test all of the following behaviors:

• When response HTTP status is 200, content type is "application/json".
• When response HTTP status is 401, content type is "application/problem+json" and problem code is "not_authenticated".
• When response HTTP status is 404, content type is "application/problem+json" and problem code is "not_found".
• When response HTTP status is 500 (server error - crash your own view), content type is "application/problem+json" and problem code is "error".