Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Roadmap #15

eamelink opened this Issue Feb 29, 2012 · 11 comments


None yet
6 participants

In this issue #4, an upcoming 1.1 release is mentioned, but that was 4 months ago. Is there any work in progress? Is there a list of features that should be built? From the top of my head:

  • Show more of the data in the resource description json in the UI
  • Show descriptions of the models in the UI
  • Allow non-GET requests from the UI

I'd like to help out, and I'm ready to fork and start making pull requests, but it would be a waste to duplicate work :)




fehguy commented Mar 6, 2012

Hi Erik,
We have a lot planned for the next release. There are different components, the spec, the UI, the server, and the codegen.

The spec's next major release will be 1.1--we were planning on some more incremental changes for that from 1.0 but right now, it looks like those will be a bit further off.

The UI next release will mostly contain a re-write of the javascript, then more functions. So please feel free to fork & send pull requests, we'll do our best to work them into any javascript changes.


acasademont commented Mar 7, 2012

+1 for the non-GET requests from the UI, now i have to set all my methods to GET in order to test them. I'll dig in the code and see what we can do about this :)

@ayush ayush was assigned Jul 9, 2012

weotch commented Jul 13, 2012

Another +1 for non-GET support


acasademont commented Jul 14, 2012

@weotch i already submitted a PR long time ago, it's already merged in the master branch ;)


acasademont commented Jul 14, 2012

In #16

@acasademont do you know if that made it into the rewrite? I've just built from master and none of the post/put parameters for the example API have got forms to submit... I could be missing something though!


ayush commented Jul 17, 2012

nope, this isn't on master yet.


acasademont commented Jul 17, 2012

Seems like there has been a major refactor of the code and now most of it is in Coffescript. So if no one made the changes in Coffescreept it's not on the master branch for the moment. If you need it you can just go back to the merge of my commit and you'll have it (i'm using that in my website with no problems at all)


@ayush ayush closed this in f2e63c6 Jul 18, 2012


ayush commented Jul 18, 2012

See here for more details: https://github.com/wordnik/swagger-ui#http-methods-and-api-invocation

Also, I've created issue #35 to track showing models in swagger-ui


ayush commented Jul 18, 2012

Also, it'll be great if someone could help test this and report any problems/regression. thx.

Shaweet! Thanks @ayush, I'll give this a go today.

@ayush ayush was unassigned by eamelink Oct 22, 2014

@mkrufky mkrufky pushed a commit to mkrufky/swagger-ui that referenced this issue Feb 26, 2016

@brhou brhou Merge pull request #15 from PagerDuty/API-674-optional-api-token
[API-678] optional api token field

@vincent-zurczak vincent-zurczak pushed a commit to roboconf/swagger-ui that referenced this issue Aug 18, 2016

@ayush ayush support for non GET methods. Closes #15 d635e78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment