search

apigee-127 / sway

A library that simplifies OpenAPI (fka Swagger) integrations/tooling.
MIT License
190 stars 92 forks source link

open API 3.0 spec support #128

Open leslie-wang opened 7 years ago

leslie-wang commented 7 years ago

OpenAPI will release version 3.0 at Feb 28, 2017. https://www.openapis.org/blog/2017/01/24/a-new-year-a-new-specification. It would be useful if this tool can support 3.0 as well.

nazarhussain commented 4 years ago

Can't share how much we are in need of this to finish. And I am willing to contribute to my available capacity. It would be nice if you put your time and efforts on planning the tasks for this release, and then community can take up the tasks and help you finish.

wickedest commented 4 years ago

@whitlockjc - I agree with the above comments - If you can put together a roadmap, then the community can help. E.g. I could fix #218 (not sure why you closed an actual roadmap issue, tbh).

whitlockjc commented 4 years ago

@wickedest It didn't seem like a roadmap issue because it's not a bug in the 2.x support or a new feature of 3.x, it's just a lack of 3.x that makes your unexpected behavior happen. So to me, completing 3.x support is what is important to track. I could be wrong.

As for everyone else, I'm down with this. I have 3.x support working locally where structural validation works and almost all semantic validation is done that was in 2.x. The delta is new semantic validation required for 3.x, and handling the new approach to requests/responses in 3.x that is not backward compatible with 2.x. I can start committing my work to master so that we can all work together if that would help.

philsturgeon commented 4 years ago

It would help, yes please!

https://github.com/notifications/unsubscribe-auth/AAAQONJ7ZHC2DLAICW6AY4TQ74NUDANCNFSM4C6MIVXA

alasdairhurst commented 4 years ago

@whitlockjc do you have any update when you will push your changes to master and we'll be able to start contributing to get the ball rolling on 3.x?