drf-writable-nested VS graphene-django

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.

Graphene-Django Graphene-Django is a powerful library that integrates the GraphQL query language with Django, allowing for the development of flexible and efficient APIs. It seamlessly combines the expressive power of GraphQL with the simplicity and elegance of Django, enabling us to design APIs that fetch only the data the clients need.

Install Graphene and Graphene-Django. Graphene is a tool that makes working with GraphQL in Python easy, while Graphene-Django adds some additional abstractions to make adding GraphQL functionality to your Django project a breeze. To install Graphene and Graphene-Django, run the following on your command line/terminal, pip install graphene graphene-django.

But if you must take a look graphene for graphql. https://docs.graphene-python.org/projects/django/en/latest/

You will find a lot of videos about Django on YouTube. If you need a REST API try DRF. If you want GraphQL try Graphene Django. For WebSockets there is Channels. If you don't want to bother with having an API for your frontend but you still want that SPA feeling try HTMX.

I've used Graphene + Graphene Django to write GraphQL APIs for several years now, but graphene-django unfortunately seems to (mostly) be abandoned now.

In conclusion, the Graphene-Django library makes it easy to get started with GraphQL integration by allowing you to use your existing Django models as the data source for your GraphQL API and automatically generate the schema. For more information, check out the documentation.

Django ninja strawberry Graphene

in my last project I used graphene to build a Django backend application with GraphQL. It seemed like the best framework to adopt graphql in python at that time in terms of stability and maturity.