drf-writable-nested VS FizzBuzz Enterprise Edition

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.

That "Hello World Enterprise Edition" looks dangerously under-engineered - I could understand it! Far better to follow the best practices demonstrated in the Fizz Buzz Enterprise Edition...

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Clean code is a balancing act - you’ll want to make sure you don’t turn your codebase into something like this.

Bu hocam https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition

amidoingitright

It seems to me that all large software projects eventually grow into "Enterprise" code. What I mean by this is something like FizzBuzz Enterprise Edition; large codebases with many layers where Design Patterns and SOLID principles are applied vigorously.

???

I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)

I'm guess that to those of us who remember when Java came out, "FizzBuzz: EE" is what we think of when we think of Java. :P

In Java I have to type a bazillion characters to get anything done! And make all these useless directories and files and InterfaceClassFactoryProtocolStreamingSerializer BS. And worry about how that executes.

C++? No bloat*, just speed

*Yes, there's some _optional_ bloat. But compared to Java? no contest.