-
Notifications
You must be signed in to change notification settings - Fork 45
Push Extensible interface up the model hierarchy #973
Copy link
Copy link
Open
Labels
area/openapiIssues related to the OpenAPI specification.Issues related to the OpenAPI specification.priority/normalIssues with default priority - these are important and interesting but can be worked on in due time.Issues with default priority - these are important and interesting but can be worked on in due time.type/enhancementIssues that represent requests for new features.Issues that represent requests for new features.
Description
Activity
Metadata
Metadata
Assignees
Labels
area/openapiIssues related to the OpenAPI specification.Issues related to the OpenAPI specification.priority/normalIssues with default priority - these are important and interesting but can be worked on in due time.Issues with default priority - these are important and interesting but can be worked on in due time.type/enhancementIssues that represent requests for new features.Issues that represent requests for new features.
Currently, the
Extensibleinterface is only accessible through version-specific interfaces (e.g.,OpenApi30Info extends OpenApi30Extensible). This means users must cast to version-specific types towork with extensions:
The
Extensibleinterface should be pushed up the common model hierarchy so that it is available onshared interfaces like
Info,Operation,PathItem, etc. This would allow a more natural API:Or ideally, if
Infoitself extendedExtensible:This is a code generator improvement — the unified model generator needs to correctly propagate common
interfaces like
Extensibleup the data model hierarchy.Originally discussed in #678.