Hi,

Thank you for the contribution.
The issue with this PR is that it's specific toserializer_class while it could also cover throttling, permissions and so on.
I'd rather see something more opened such as "it takes as arguments the class properties such as serializer_class"

I see, actually, right after the example, it says exactly that. I just didn't get it. Still, I would like to contribute the fix of the example code, passing theserializer_class argument (and useself.get_serializer() if I'm not mistaken, see review). I think that the example caused the confusion with meand others trying to use a custom serializer class.

The kwarg is necessary, regardless of usage inside the function. Without the kwarg, the generated doc will show theUserSerializer form, not thePasswordSerializer form. That is the reason why I had trouble with understanding the decorator, I didn't knew how to change the form.

I feel that it might be common that extra actions have other inputs than the normal actions. Therefore I think it's a good idea to show correct usage of another serializer.

Hi@soerface. Yes, right. I'm thinking then we should rephrase alittle bit to spell that out. (Note emphasis onlittle.)

Happy if you want have a pop at that. If not I'll give it a look over.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.