Add OpenAPI Extensions support for Route documentation #202
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements support for OpenAPI Extensions in route documentation, allowing developers to add custom metadata to their API routes.
Usage Example
Extensibility
While this PR focuses on adding extensions support to
RouteConfig
, the OpenAPI specification allows extensions on many other objects. The foundation laid here can be easily extended to other configuration classes (likeRequestConfig
,ResponseConfig
,ParameterConfig
, etc.) when needed in the future.