Schema support for serializer_class with @api_view

[blueyed]

The WrappedAPIView returned/created by the @api_view decorator handles decorators like @renderer_classes, but not @serializer_class.

Having information about the (input) serializer appears to be important for generating schemas however.

I think this would have helped with the underlying issue that #4285 fixed, and is maybe also what #5630 (comment) refers to?!

[carltongibson]

Hey @blueyed. This is just the division between APIView and GenericAPIView. The api_view decorator handles the former, but not the latter. (And serializer_class is defined on GenericAPIView...)

The comment you link (I was wondering where that was...) is looking for more API (on APIView) to add an extension point for dynamic view inspector class selection, rather than @ api_view's support (or not) of the GenericAPIView API.

[blueyed]

What do you suggest then to get proper documentation / schema?
Not using @api_view, or create a custom decorator that would use GenericAPIView instead?

[carltongibson]

You'd need to pass an AutoSchema subclass that knew about your view. Either that or, yes, use GenericAPIView, probably just as a class-based view.

You can use any means you like, but the built-in support leverages GenericAPIView.