while performance is improved with list serializers for models that included additional computed properties, curiously this implementation only works when the server receive a single request, and serialization of that request finishes before the next request.
If however the server receives concurrent requests, some of the child item representations receive all null values. Both requests are return 200 with no errors logs... On Friday, May 17, 2019 at 6:47:34 PM UTC-4, Kyle Edwards wrote: > > I get the feeling this isn't a great idea, especially if nested > serializers are involved > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-rest-framework/4d096ab3-ba82-47fc-9f98-d500d3f53a4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
