-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Swagger spec 2.0 #29
Comments
yes i'm targeting it for the next major release, i don't have a timeframe for it yet, if i was to guess i would say its not going to be for a couple of months |
+1 from me as well. |
swagger-compat-sped-parser could be the way to go. There's a migrator that could used ease up the transition but better yet there seems to be jackson based models that could be used instead of doclet models if 1.2 support is no longer deemed as a must. |
I would prefer to see support of the 2.0 spec instead of 1.2. If 1.2 is needed just used the older version of the doclet. |
Any update on the timeframe for the support of 2.0 spec? |
Same question, prompted by swagger-api/swagger-codegen#1241 (comment). I don't need an accurate date, but a rough guess would be helpful. Is this expected to take weeks, months, or years? |
Sorry for +1ing, any indication on whether this can be at all expected? |
it's really hard to put a timeframe on this, this project is something that I can only work on periodically in my spare time, I'd love to push out the 2.0 release in the next 6 months but atm I have a lot of commitments so can't give any firm timeline |
@conorroche Thanks for the update. |
Any plan to support 2.0?
The text was updated successfully, but these errors were encountered: