drf-writable-nested VS drf-extra-fields

use the quite popular, third party library DRF Writable Nested do it on your own I would recommend choosing the second option at least once, so you will know what’s going underneath.

We have used this successfully for years. https://github.com/beda-software/drf-writable-nested I have never understood why this is not a default and used by more devs. Hope that helps

Yeah OK, I'll just change and comment where appropriate (albeit I did not really test this code nor did use a proper text editor): class UserListCreateView(generics.ListCreateAPIView): permission_classes = [permissions.IsAuthenticated] serializer_class = AccountSerializer There is a built-in permission for authentication. But if that does not suit you, you can implement your own. (e.g. IsTeacher, IsSchool etc.) Also, it seems like you are returning teachers as a nested data, so you might need to implement your own logic for the serializer to be writable, or use drf-writable-nested ``` def get_queryset(self, request): if self.request.user.account_type == "teacher": return Account.objects.all().filter(username=self.request.user)

Combo of drf-writeable-nested and my own tools.

You could also make use of https://github.com/beda-software/drf-writable-nested which I recently found. It makes dealing with nested fields and relations super easy.

If we want to create or update a nested model relation. drf-writable-nested is a package that comes for rescue; it supports nested serializer both create and update operations. it also available supports for OneToOne, ForeignKey, ManyToMany. https://github.com/beda-software/drf-writable-nested

drf-writable-nested does that for you.

Also, I suggest you look at the writable nested serializers package as it will simplify your code a lot.

drf-extra-fields has many more custom fields, like Base64ImageField, it will accept a image file as base64 encoded and will return as image file. please checkout the https://github.com/Hipo/drf-extra-fields for more information