Sphinx HTTP Domain
Description
Sphinx plugin to add an HTTP domain, allowing the documentation of RESTful HTTP methods.
This is very rudimentary and experimental code at the moment.
HTTP methods
You can document simple methods, wrap any arguments in the path with curly-braces:
.. http:method:: GET /api/foo/bar/{id}/{slug}
:arg id: An id
:arg slug: A slug
Retrieve list of foobars matching given id.
Query string parameters are also supported, both mandatory and optional:
.. http:method:: GET /api/foo/bar/?id&slug :param id: An id :optparam slug: A slug Search for a list of foobars matching given id.
As well, you can provide types for parameters and arguments:
.. http:method:: GET /api/foo/bar/{id}/?slug
:arg integer id: An id
:optparam string slug: A slug
Search for a list of foobars matching given id.
Fragments are also supported:
.. http:method:: GET /#!/username :fragment username: A username Renders a user's profile page.
Plus, you can document the responses with their response codes:
.. http:method:: POST /api/foo/bar/ :param string slug: A slug :response 201: A foobar was created successfully. :response 400: Create a foobar.
To refer to an HTTP method, use :http:method::
.. http:method:: GET /api/ :label-name: get-root :title: API root The :http:method:`get-root` contains all of the API.
HTTP responses
Documenting responses is also simple:
.. http:response:: Foobar object
A foobar object looks like this::
.. source-code:: js
{
'slug': SLUG
}
:data string SLUG: A slug
:format: JSON
To refer to an HTTP response, use :http:response::
.. http:response:: Foobar object A :http:response:`foobar-object` is returned when you foo the bar.
Installation
Run pip install sphinx-http-domain.
Then, add sphinx_http_domain to your conf.py:
extensions = ['sphinx_http_domain']
Development
Version: pre-Alpha
For contributions, please fork this project on GitHub!
Contributors
Simon Law (https://github.com/sfllaw)
Metadata
Release files for sphinx-http-domain 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sphinx-http-domain-0.2.tar.gz | 9.6 kB | Without provenance | Details for sphinx-http-domain-0.2.tar.gz |
Release files / sphinx-http-domain-0.2.tar.gz
| Download URL | sphinx-http-domain-0.2.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e3f29bab7a00ccc40a8f58400a77522780aa262d6a5c140147721da8e25f2fb
|
|
BLAKE2b-256 checksum How to use checksums |
2f0f8cba5fa05ae80a96cbe768fac6e628b1e65edfecff88d0b67240d92e6d1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sphinx-http-domain 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.