Skip to content
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

Design and build annotated API using django and swagger with documentation #18

Open
meganmckissack opened this issue Feb 21, 2017 · 6 comments

Comments

@meganmckissack
Copy link
Member

meganmckissack commented Feb 21, 2017

(http://swagger.io/)

@hassanshamim
Copy link
Collaborator

Seems like an easy addition: https://github.com/marcgibbons/django-rest-swagger

@ron-s
Copy link

ron-s commented Mar 6, 2017

added swagger (branch: add-swagger) using official framework tutorial:
http://marcgibbons.github.io/django-rest-swagger

@jimtyhurst
Copy link
Contributor

The Budget web service is now displaying a Swagger-generated API description, but it is not as useful as it could be. If you look at a sample, like Swagger's Pet Store example, the endpoint descriptions specify parameters, HTTP error code conditions, sample JSON message content, etc., but our API description has none of those. If someone can tell me the annotations or documentation format for specifying those values for a Python function, I would be glad to enhance the documentation. I know how to use Swagger annotations for Java methods, so I did some web searching, but I could not find how to do it for Python.

@MikeTheCanuck MikeTheCanuck changed the title Design and build API using django and swagger with documentation Design and build annotated API using django and swagger with documentation Mar 20, 2017
@MikeTheCanuck
Copy link
Collaborator

Updated title to reflect the gap that @jimtyhurst identified.

@jimtyhurst
Copy link
Contributor

See marcgibbons/django-rest-swagger#549 which explains that it is a known issue that the framework that we have chosen does not implement the parts of the Swagger specification that deal with path parameters, query parameters, possible values of parameters, sample return values, error conditions, etc. Also see hackoregon/emergency-response-backend#21 which suggests a workaround.

@mxmoss
Copy link
Contributor

mxmoss commented Apr 29, 2017

Seems like this issue has been addressed. Can we close it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants