Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
https://github.com/ruby-grape/grape-swagger/pull/311 has been merged onto a branch called swagger-2.0. Looking forward to more PRs to move that forward!
So we have a 2.0 branch. Who wants to take ownership, get that merged onto master, released, etc.? What remains to get done? @LeFnord maybe?
I am not in love with the idea of two gems for different versions of the spec. I think people just want to upgrade to the swagger 2.0 spec soon...
I'd like to do the following: 1. Release 0.10.5. 2. Branch 0.10.5 into 0.10.x, continue releasing bug fixes only in a 0.10.x series compatible with 1.5 3. Merge swagger-2.0 onto...
@LeFnord I invited you the swagger-maintainers org. I am happy to help with whatever you need. You should PR yourself under grape-swagger in https://github.com/ruby-grape/ruby-grape.github.io/blob/da76718ff723d8e6e6a3f45972045ce133220842/team/index.md. Drop me an email at dblock[at]dblock[dot]org...
definitely would need a good UPGRADING.md change to understand all that's changing and will take a look at the details in code, too. @namusyaka would appreciate another pair of eyes
I am going to change this from "bug" to "feature request". We still want this :)
Thanks. This isn’t blocking grape, we just leave jruby-head and other *-head to keep finding issues early. If some PR turns all builds green we can close this.
Probably not right now, but we should support it. PRs welcome!
If you think it worked with an older version of Grape, bisect back a couple of major versions?