[
https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5555:
---------------------------------------
https://github.com/oasis-tcs/odata-openapi looks to be the most promising starting point.
It's for openapi 3 - is there a reason you want 2.0 support?
This work seems to account for most of my concerns. It generates explicit paths to two
entity levels and shows all possible odata url parameters for each path. It also shows
the full result entity, such that usage of expand would be accounted for. $expand though
seems limited - as the openapi does not seem to describe using query options in parens in
the expand e.g. {code}$expand=*($levels=1){code}
So it's very verbose, but does a reasonable job of representing the api.
Create OpenAPI (swagger) metadata document based on OData
---------------------------------------------------------
Key: TEIID-5555
URL:
https://issues.jboss.org/browse/TEIID-5555
Project: Teiid
Issue Type: Enhancement
Components: OData
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 12.1, 11.2.2
Automatically generate Swagger metadata document based on OData metadata such the tools
like 3Scale can understand the metadata through existing plugins until OData specific
plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not
considered.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)