wq.db.rest.serializers.ModelSerializer's context contains no request

[tomaszn]

My serializer should calculate some values which depend on the user's account.

I subclassed ModelSerializer (from wq), and can't find a way to reliably determine the request in the constructor (to prepare information for to_representation method to use for every serialized instance).

According to https://stackoverflow.com/a/34617511/1762343, the request should be in self.context dict, but I can only (sometimes) find 'router': <wq.db.rest.routers.ModelRouter> there.

[sheppard]

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.

[tomaszn]

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

wq.db/rest/routers.py

Line 214 in 6fb0c46

return serializer(obj, many=many, context={'router': self}).data

You are right for the simple queries.

[tomaszn]

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

[sheppard]

I added the request to the context for parent objects.