Enhancement: Serve openapi routes under multiple path prefixes #3339
Labels
3.x
This is related to Litestar version 3
area/openapi
This PR involves changes to the OpenAPI schema
Enhancement
This is a new feature or request
Summary
We've seen a pattern where an
OpenAPIController
subclass would be registered directly onto the application, and (prior to 2.8) implicitly via theOpenAPIConfig
object, e.g.,:This pattern supports serving the openapi schema routes both under
/schema
and/some-prefix/schema
.We need to consider how this pattern would be implemented in v3 when the OpenAPIController object doesn't exist.
ref: #3337
Basic Example
Drawbacks and Impact
No response
Unresolved questions
No response
Note
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard
The text was updated successfully, but these errors were encountered: