| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Also change any docutils.sourceforge.net link to io
top level domain.
|
| |
|
|
| |
Used in add_autodocumenter docstring
|
| | |
|
| | |
|
| |\
| |
| | |
Fix #8860: doc: Usage of recipe directive is wrong
|
| | | |
|
| |/
|
|
|
|
| |
The pre check in the `ReceipeDirective.add_target_and_index() was wrong.
It checkes non-existing option "noindex", but it should check "contains"
option instead.
|
| |
|
| |
I missed that there are actually two sections explaining extensions in the docs and just saw the examples based one. This lead to me thinking "kind of lousy documentation, but that's probably par for the course". Would there have been a pointer to the detailed extension API description it would have saved me hours of guesswork.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Keep imports alphabetically sorted and their order homogeneous across
Python source files.
The isort project has more feature and is more active than the
flake8-import-order plugin.
Most issues caught were simply import ordering from the same module.
Where imports were purposefully placed out of order, tag with
isort:skip.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
development
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Closes #6751
|
| | |
|
| | |
|
| |
|
|
|
|
| |
These were causing flake8 failures.
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| |
|
|
|
|
|
|
|
|
| |
todo:
- Subclass SphinxDirective instead of Directive
recipe:
- Remove unnecessary '__init__' methods
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
helloworld:
- Return version metadata from extension
- Use 'reST' instead of 'rST'
- Don't use single backticks
todo:
- Return version metadata from extension
- Link to events section of API guide, rather than entire document
- Include name of phases in when describing build phases
- Use more method cross-references where possible
- Fix typo in usage example
recipe:
- Return version metadata from extension
- Rework code to simplify things
- Remove docstrings from 'generate' functions, which are simply
duplicates of the original docstring
- Rename 'rcp' directive to 'recipe', the 'reref' role to 'ref', and a
whole lot of variables to something more grokable
- Fix typos in both documentation and code
I've also fixed up the docstrings for some of the 'domain' functions to
make them render a little nicer (they took me a while to figure out).
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is based on a post from opensource.com [1] and demonstrates how one
can use indexes for cross-referencing and domains to group these indexes
along with domains and roles. The source code was taken from [2] after
getting the license changed [3].
[1] https://opensource.com/article/18/11/building-custom-workflows-sphinx
[2] https://github.com/ofosos/sphinxrecipes
[3] https://github.com/ofosos/sphinxrecipes/issues/1
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| |
|
|
|
|
|
| |
This avoid duplication and could conceivably let us test this stuff in
code later on.
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| |
|
|
|
|
|
| |
Adopt the same format as was recently added in the "hello world"
tutorial, making this more of a walkthrough as expected from tutorials.
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| |
|
|
|
|
|
| |
Nothing to drastic going on here, but this format works better for other
tutorials we're adding.
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|