Swagger/OpenAPI 3.0 support?

[tckb]

Now that OpenAPI 3.0 (stable) specification has been released, do we have any plans for working on the 3.0 support?

Thanks!

[webron]

We don't have plans for it in the immediate future.

[stefanholzmueller]

@webron Any idea what needs to be done to upgrade to the 3.0 spec? Could you use some help? Or will OpenAPI 3.0 never be supported by this project? I'd just like to know if that decision has been made.

[webron]

swagger-play's usage is one of the lowest we have in the various projects we maintain. As such, doing the work to support Play, especially given that Play's version are backward incompatible and cause issues with every release - is very time consuming and we don't really have the capacity to actively work on it.

That said, I'm considering the options to make this happen. If anyone in the community has input on this, I'd be happy to hear.

[gmethvin]

We happen to be using this library at Iterable and are maintaining a fork, including some of the other unmerged changes from this repo: https://github.com/Iterable/swagger-play. If anyone wants to help with OpenAPI 3 support, I'm happy to help with the Play aspects, though I'm not that experienced with the Swagger APIs.

I think one reason this library is underutilized is that there are a few competing Swagger implementations for Play. One of them is https://github.com/iheartradio/play-swagger, which seems more actively maintained and now supports OpenAPI v3, but uses comments in the routes file as opposed to annotations.

[jeremylaier]

Any new updates?

[JayZYan]

Any updates please?