T. Franzel

Hi all! I don't want to hijack this issue, but i would like to inform you guys of our DRF OpenAPI 3.0 schema generator: https://github.com/tfranzel/drf-spectacular A few of the mentioned...

- `detail=True` only determines where the endpoint is mounted. irrelevant for the endpoint schema itself. - spectacular response suggests there is a `pagination_class` present on that view/action. The pagination logic...

@kiblik I can't comment on the other things but `detail` works 100% like I said, trust me :smiley: ```python /x/ # list /x/{id}/ # retrieve /x/action # action with detail=False...

yes exactly. awesome! I will prepare a PR with tests.

Hi Glenn, I get your point. This has been raised a couple of times. See here for my previous comment https://github.com/tfranzel/drf-spectacular/issues/431#issuecomment-862738643 > The request body applicable for this operation. The...

Sure! I'll leave this open as a reminder for 3.1 support.

Hi, in theory we do support extensions for custom list serializers, but you are not using a `ListSerializer` but instead a `ListField`, which is quite similar but still different. If...

I see. That looks like a bug. The `enum` is not properly handled in case of `many=True` ```yaml - in: query name: status schema: type: array items: type: integer enum:...

`@extend_schema*` is the indented interface for one-off changes to the schema. Also, documentation which is too far removed from the code goes stale very quickly. So this is by design....

I would call that a lot less clean. You are writing a custom schema with 3 extra layers of boilerplate. ```python # schema.py from drf_spectacular.openapi import AutoSchema data = {...