API documentation overhaul#3078
Conversation
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
bcafca7 to
f815175
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
92440e9 to
e787e23
Compare
|
Refer to this link for build results (access rights to CI server needed): |
e787e23 to
5693792
Compare
|
Refer to this link for build results (access rights to CI server needed): |
5693792 to
4238e01
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
dfa8bd5 to
932ee5c
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
I may need to add more keys to the definition - CIAB has quite a few less than production environments, but I don't understand all of the nuances there
79814a8 to
5006afa
Compare
|
Refer to this link for build results (access rights to CI server needed): |
What does this PR do?
This PR is an overhaul to the way the API documentation is laid out. It gives each unique request path its own page - but only considers request paths unique if they differ after the
/api/1.x/portion. Rather than a new page in every minor API version, the docs will use theversionchanged,versionadded, anddeprecatedreStructuredText directives to indicate changes between minor versions.Also, each page follows the same, consistent formatting using proper section headings that allow links to specific parts of specific methods on an endpoint to be "link-able" - as well as the (now fully-HTTP wherever possible) request and response sections.
Grouping of endpoints by function is not currently implemented, but will probably be done when I finally get around to fixing up the index page with an explanation of the new layout.
Which TC components are affected by this PR?
What is the best way to verify this PR?
Build the documentation, and evaluate if the new layout is effective.
Check all that apply