Hello DRF Community, After posting this question <https://stackoverflow.com/questions/44475733/drf-filter-from-url-instead-query-parameters> (and answering it by myself) I was wondering what are the best practices the community currently uses to organize nested resources like the one in my example.
What I mean is that there are numerous ways to do this. In my example, I handle everything in the UserViewSet class, but I could, for instance, handle the routing in a CompanyViewSet and call UserViewSet from there. I could also handle everything on CompanyViewSet. I don't feel like the way I handle it in my answer is the best way possible, but yet I can't see what could be a better way of handling that. I'm specially worried about scale (not performance-wise, but from a code organization viewpoint). For me this is specially hard to think about as I am just starting with DRF. Thanks, Lucas. -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
