-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Document the API #814
Comments
I totally agree! I have long intended to write a tutorial with full examples of how you can create datasets and models and do inference using the API but never got around to doing it. Also, I was planning to change some of the API in #616 so I found it convenient to have it undocumented at the time :-) We used to have auto-generated API docs in https://github.com/NVIDIA/DIGITS/blob/v2.2.1/docs/API.md but this was removed. It might be worth improving the inline doc and resurrecting this auto-documentation. |
That in-line doclooks great. Maybe resurrect that phoenix? On Tue, Jun 7, 2016 at 10:46 AM, Greg Heinrich notifications@github.com
|
I removed I couldn't find a way to order the decorators on views properly so that |
Hello I have pushed #964 to help there. It is not a proper API reference but it shows examples of how to use the API. Writing a detailed documentation would be difficult sine most of the magic is in the form fields, which aren't easy to add to the inline documentation. |
Hi guys. Currently the API functionality can only be browser by reading through the code. There is no overview of any kind, although the API functionality is, of course- and as intended, very neat.
I remember that before realizing there was an open API at all, I found something in a tutorial along the lines of:
curl localhost:5000/models/images/generic/infer_many.json (...)
One can never know about the API and its functionality without going through all the source code, therefore I think it's nice at least have a concise list-ish overview of all the routes and the potential arguments.
The text was updated successfully, but these errors were encountered: