You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use this extension with sphinx frequently at work. It's very useful and I find the documentation accurate and verbose.
I recently noticed something (and I believe this has been the case since day 1 of me using this extension). It's not a functional limitation, but purely an aesthetic one.
the rendered output looks like the following (divided by the horizontal ruler)
API Summary
Resource
Operation
Description
GET /rest
Serves as an entry-point to implementation
Accounts
GET /rest/v1/accounts
Shows information about accounts
--
--
--
Root
GET /rest/v1
Shows supported resources and services
--
--
--
API Details
GET /rest HTTP/1.1
Serves as an entry-point to implementation
Example Request:
...
Example Response:
...
GET /rest/v1 HTTP/1.1
Shows supported resources and services
Example Request:
...
Example Response:
...
GET /rest/v1/accounts HTTP/1.1
Shows information about accounts
Example Request:
...
Example Response:
...
The examples above are relabeled but the order is maintained from the generated doc. The Details section obeys the :order: directive, but the Summary section violates it.
It appears that if a <resource> (an optional) value is given, flaskqref orders the APIs in a lexicographical order of the resource column rather than the one set by path
I use this extension with sphinx frequently at work. It's very useful and I find the documentation accurate and verbose.
I recently noticed something (and I believe this has been the case since day 1 of me using this extension). It's not a functional limitation, but purely an aesthetic one.
I use both:
It generates a nice summary table and an API list.
The
index.rst
looks like the followingthe rendered output looks like the following (divided by the horizontal ruler)
API Summary
API Details
GET /rest HTTP/1.1
Serves as an entry-point to implementation
Example Request:
...
Example Response:
...
GET /rest/v1 HTTP/1.1
Shows supported resources and services
Example Request:
...
Example Response:
...
GET /rest/v1/accounts HTTP/1.1
Shows information about accounts
Example Request:
...
Example Response:
...
The examples above are relabeled but the order is maintained from the generated doc. The
Details
section obeys the:order:
directive, but theSummary
section violates it.It appears that if a
<resource>
(an optional) value is given,flaskqref
orders the APIs in a lexicographical order of theresource
column rather than the one set bypath
Software packages
The text was updated successfully, but these errors were encountered: