-
Notifications
You must be signed in to change notification settings - Fork 364
Document the API using Swagger #455
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
Comments
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/106128498. |
Hi Chris, I've recently been seeing more requests like yours to use swagger to help with client generation and verification. [1] https://www.pivotaltracker.com/story/show/104040832 |
Hi, I hadn't come across Slate before. It looks like it would also be an improvement. While being able to generate stubs/tests from a Swagger file would be good I understand the extra work that would involve. Slate would be much appreciated. Thanks for the quick response. |
For people implementing clients to the API the documentation is the only resource available. It several areas the quality of the documentation is very poor meaning ambiguity can creep in to implementations. It also takes a lot of time write an implementation and a machine readable format would help speed things up. Finally, a machine readable format would help with testing of a client library against a particular version of the specification.
So far I'm aware of Java and Node based clients being created and I imagine the CLI implementations could benefit as well. Swagger is the de-facto format for specifying APIs and includes a great viewer for navigating an API. http://swagger.io/
The text was updated successfully, but these errors were encountered: