Any plans to migrate to swagger 2.0?

[NeilCross]

Are there any plans or timeframes to migrate to swagger 2.0? If not, would you consider taking pull requests?

[superstator]

Well, the honest truth is no - no plans or timeframe. I have a half-finished cleanup that has been on the back burner for a while, so I don't know when I'll get around to looking at 2.0. For the same reason, I'm hesitant to tell you to just go for it and send a pull request.

That said, if the changes are minor (I really haven't even looked at the updated spec), or if you're already going down that road, please do feel free. I don't want this to languish on my account.

[NeilCross]

Thanks for the reply Adrian, I'd read in a few of the issues that you'd been working on a cleanup so obviously I wanted a lay of the land before I took the leap.

I'm not extremely familiar with v2 of swagger but i do know that it isn't a set of incremental improvements, there's breaking changes between it and 1.2 so i'm inclined to name or inject a serializer for the required output version, i expect the current attributes cover most of the detail required for v2, just not the output syntax.

Anyway thanks for the info, I'll be sure to be in touch if i make progress on this one.

Cheers, Neil

On 29 October 2014 14:33, Adrian Black [email protected] wrote:

Well, the honest truth is no - no plans or timeframe. I have a half-finished cleanup that has been on the back burner for a while, so I don't know when I'll get around to looking at 2.0. For the same reason, I'm hesitant to tell you to just go for it and send a pull request.

That said, if the changes are minor (I really haven't even looked at the updated spec), or if you're already going down that road, please do feel free. I don't want this to languish on my account.

— Reply to this email directly or view it on GitHub https://github.com/superstator/Swaggeratr/issues/69#issuecomment-60869200 .