wq.db.rest.serializers.ModelSerializer's context contains no request about wq.db HOT 4 CLOSED

The router initializes the serializers at startup to generate the configuration object. So, there isn't any request in the context at that time. But once you get to actually rendering and parsing records the request object should be there. So, you just need to have a check or a fallback when dealing with code that relies on request. One way to do this would be to wait until to_representation to load the user information.

from wq.db.

I see now that the request object is missing in the list queries for parent objects; the context is initialized with the router only:

You are right for the simple queries.

from wq.db.

This way I managed to add context.request to serializers:
https://stackoverflow.com/a/31724701/1762343

from wq.db.

I added the request to the context for parent objects.

from wq.db.