You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw a thread from the original go openapi parser that indicated this is the repo to use for OpenAPI 3 support. Last update is 3 months ago.. so I have hope that this is being worked on. But I can't find anything that talks much about this. The README of the repo leaves a lot to be desired. How do we use this in our own code to parse OpenAPI 3 definitions? Does it work with multiple files with refs or does it require some sort of aggregation before parsing? Does it parse in to a usable SDK where by I can iterate through paths, components, tags, vendor extensions, etc?
It would be fantastic to get some info with regards to how much of the spec is supported, some examples of how to use this SDK in our own code, some timeline as to when the full spec will be supported, etc.
Thank you.
The text was updated successfully, but these errors were encountered:
I saw a thread from the original go openapi parser that indicated this is the repo to use for OpenAPI 3 support. Last update is 3 months ago.. so I have hope that this is being worked on. But I can't find anything that talks much about this. The README of the repo leaves a lot to be desired. How do we use this in our own code to parse OpenAPI 3 definitions? Does it work with multiple files with refs or does it require some sort of aggregation before parsing? Does it parse in to a usable SDK where by I can iterate through paths, components, tags, vendor extensions, etc?
It would be fantastic to get some info with regards to how much of the spec is supported, some examples of how to use this SDK in our own code, some timeline as to when the full spec will be supported, etc.
Thank you.
The text was updated successfully, but these errors were encountered: