Content negotiation vs serializer

[Ola]

Hello,

I have a usecase where I need to implement different serializers for
different format. settings.py have a list of different
DEFAULT_RENDERER_CLASSES and PARSERS. I would like to take adventage of
HyperlinkedIdentityField in some of the serializers but not all. What is
the best way to do it?

A.

[Thế Bùi Công]

u can review this:
https://stackoverflow.com/questions/40747927/how-to-write-a-custom-serializer

Post by Ola
Hello,
I have a usecase where I need to implement different serializers for
different format. settings.py have a list of different
DEFAULT_RENDERER_CLASSES and PARSERS. I would like to take adventage of
HyperlinkedIdentityField in some of the serializers but not all. What is
the best way to do it?
A.
--
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
For more options, visit https://groups.google.com/d/optout.

[Carlton Gibson]

I have a usecase where I need to implement different serializers for different format.

In `get_serializer()` or `get_serializer_class()` inspect the format and act appropriately.

[Ola]

I agree to_presenation is to late to do it thanks for suggestions