T. Franzel

hi @mblayman, i'm not completely sure i get the full scope of your issue. > In 2eaac13#diff-136013649b2fdf2f5496f11ae4591a56cc9d5d340869338b544905cb40b608f4L216, the ability to get the API version from the request was removed. i...

i see. for path/namespace versioning that does not look too bad, but header versioning would break in one schema and we do support that too. I must also assume that...

one more thing i just implicitly mentioned but never verbalized explicitly. spectacular **does guarantee** that your generated schema is valid and without conflict (when there no warning in that regard)....

aweome! glad your found a solution. i'll rename the issue and leave it open for future reference. i can see this feature happening with 1-2 more independent requests.

Hi @Headmaster11, that is a good point. The default actually comes out of DRF: https://github.com/encode/django-rest-framework/blob/71e6c30034a1dd35a39ca74f86c371713e762c79/rest_framework/filters.py#L322 So we may either fix it upstream or introduce an override (`OpenApiFilterExtension`) on our side.

hi @BorisBeast, the plan is definitely there. imho `SwaggerUI` and `openapi-generator` are the main usages of spectacular and and the last time i looked they had not added support yet....

small update: * `jsonschema`, our validation dependency received an update to support `Draft 2020-12` (required for 3.1) * our whole test suite is green wrt. OpenAPI 3.1 validation (iff `3.0.3`...

@pranto157 this issue is dedicated to OpenAPI 3.1. your issue is unrelated.

What can is say. When I came up with this, I did not expect a lot of people would use it except me. :smile: Now that it is seasoned and...

I just remembered that we do something similiar with pagination: `PaginatedCarList`