One of the developers here. We have a lot of plans for this. We will allow you to download client SDK and many different kinds of server code based on your API design. We think it's a good tool to shape your API before implementing all the business logic in your server/client code
I... think I like it? There needs to be a lot more documentation though, I'm not entirely clear what the output of this tool is... does it spit out code I can drop into a project of mine? Is it just a tool to mock up an API, and give some sort of playground for API consumers to use? Is it something else?<p>I think any of the above would be useful, I'm just not sure which one(s) this is trying to be.
This looks promising. I think there is value from separating the spec from the implementation details. Here is a dream workflow:<p>* version controlled canonical specs and documentation of API using apistudio.io<p>* use existing Swagger extensions to build out Swagger spec from implementation<p>* Some tool to automatically compare/verify canonical swagger spec with spec generated by framework plugin
I think this is a step backward.<p>Its amusing to be able to mock out some APIs but the fact that its just a mock makes it a waste of time.<p>There are already projects that let you automatically build out a swagger page from a jax-ws project (or your language of choice). Actually making the objects and stubbing out endpoints in code should be just as fast as playing with a new custom schema language.