-
Notifications
You must be signed in to change notification settings - Fork 200
ETA for 3.0? #158
Comments
I had originally planned to release a v3 of Swagger Express Middleware with up-to-date dependencies and support for both Swagger 2.0 and OpenAPI 3.0. But that has proved too challenging, for a few reasons:
However, my focus at work is about to change back to Swagger Express Middleware, so I'll be able to start devoting time to this again. And my new plan is to split this package up into separate packages that are well-contained and independent from each other. I will focus on supporting OpenAPI 3.0, but may also create an adapter package that adds support for Swagger 2.0 as well. By creating smaller modules, I'll also be able to release them sooner. Rather than having to wait until everything is totally done, I'll be able to release each package as soon as it's done. And since many people only use a subset of Swagger Express Middleware's functionality, those people will be able to switch to the new packages as soon as the subset that they need are done. |
Is there a workaround for this? Do I need to move back to swagger 2.0? |
New information? |
im sure there exists a few projects which have attempted to tackle this, ive had some luck with https://www.npmjs.com/package/openapi-validator-middleware |
Is there any type of estimate for when 3.0 will be out of alpha and ready for production?
Just a general time frame
1-3 months?
3-6 months?
6-12 months?
12+ months?
Thanks!
The text was updated successfully, but these errors were encountered: