-
Notifications
You must be signed in to change notification settings - Fork 17
Document the public API #99
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
I would like to be assigned this issue please ❤️ |
Just an update, this is coming along now what I'm going to do I think is open a PR early on this, there are things I don't know and I will obviously have missed because, well, it's not my app :D However, coming together. Regarding the testing, I'm wondering if it's ok if I open in a different PR? Just stops 'one big pr' hitting Cheers, ( sneak peak of the documentation viewer being served from inside the docker.. ) |
Absolutely. The primary goal of this issue was to document, not test. It's looking good! |
@scampiuk, just wanted to check in since October is almost over. Can you make a PR for this? |
Yes sorry, I hate it when I sign up for things then forget I've got a job and two kids and stuff! :D I've got this week off work so i'll push the document up over the next 48 hrs |
…-api Feature/#99 document the public api
The API, while undocumented, is currently public. It would be nice to have a page dedicated to explaining the various routes and payloads for developers to use if they so choose.
Perhaps Swagger or something similar would make sense for this.
Dredd could be used to test the documented API.
The text was updated successfully, but these errors were encountered: