Closed Bug 986421 Opened 11 years ago Closed 11 years ago

Need clear documentation of the server APIs

Categories

(Hello (Loop) :: Server, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: standard8, Assigned: alexis+bugs)

References

Details

(Whiteboard: [qa+][mlp-server?])

Attachments

(1 file)

48 bytes, text/x-github-pull-request
abr
: review+
dmosedale
: feedback+
standard8
: feedback+
NiKo
: feedback+
Details | Review
The server API documentation is highly insufficient. I currently have the following issues: - Some requests require parameters in JSON bodies, others require them in querystrings - It is unclear the intention of some of the parameters, and what their intended values and scales are. - The return values are not documented. The API documentation really should be updated in sync with the bugs that are implementing/changing the APIs.
Assignee: nobody → alexis+bugs
Depends on: 984383
Should reviewers be requiring documentation updates for r+? I'd say yes.
dmose we will definitly do that in the future. The hardest part is to setup the first layout. Tomorrow we will land the first documentation draft and after that we will require documentation changes for every PR. :)
Great; glad to hear it!
Attached file link to github PR
Attachment #8396763 - Flags: review?(adam)
Attachment #8396763 - Flags: feedback?(standard8)
Attachment #8396763 - Flags: feedback?(dmose)
I did a pull request with some basic documentation. Please provide me any feedback on it. You can have a look at the rendered documentation here, in the meantime I put a preview version here: http://alexis.notmyidea.org/services-docs/loop/
+1 because QA loves documentation.
Whiteboard: [qa+]
Attachment #8396763 - Flags: feedback?(nperriault)
In my experience it helps to give curl example for API calls.
Maybe using the HTTPie <https://github.com/jkbr/httpie> format?
That's a brilliant idea! I've updated the docs with full examples. Updated the temporary location : http://alexis.notmyidea.org/services-docs/loop/apis.html#apis
Comment on attachment 8396763 [details] [review] link to github PR Commented on PR, looks generally good to me.
Attachment #8396763 - Flags: feedback?(standard8) → feedback+
Comment on attachment 8396763 [details] [review] link to github PR Looks very good to me as well.
Attachment #8396763 - Flags: feedback?(nperriault) → feedback+
Comment on attachment 8396763 [details] [review] link to github PR Looks good to me too. Presumably, this wants to be linked to from the wiki page and the README once it's live.
Attachment #8396763 - Flags: feedback?(dmose) → feedback+
Comment on attachment 8396763 [details] [review] link to github PR This looks correct for MLP. Thanks.
Attachment #8396763 - Flags: review?(adam) → review+
Waiting for the docs to regenerate. In the meantime they're available here: http://moz-services-docs.readthedocs.org/en/latest/
No longer blocks: loop_mlp
Alexis -- Is this bug completed for MLP? Thanks.
Flags: needinfo?(alexis+bugs)
Whiteboard: [qa+] → [qa+][mlp-server?]
For whatever reason the docs fails to generate, that's why I'm keeping it open. Dan, can you have a look there and tell me why the docs are not generating correctly on docs.services.mozilla.com ? (the svn seems up to date, but the actual docs aren't).
Flags: needinfo?(alexis+bugs) → needinfo?(dmaher)
It should be noted that I no longer work in the webops team, and thus, am no longer responsible for this mechanism. That said, I looked into it, and determined that the cause of the problem was a simple logic failure in the update script, which would cause it to not pull the repo under a specific circumstance. That has now been fixed, so the site should update as expected from now own. I apologise for the inconvenience.
Flags: needinfo?(dmaher)
Oh okay, thanks dan for the convenience then ;)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Yep.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: