I often use nested lists to define and discuss some content. Like a tool->feature->error list:
Sphinx
Build HTML
Directive not found
Build PDF
...
git
Commit changes
...
When everything is discussed, this list gets transformed by hand to Sphinx-Needs objects.
This is an annoying and stupid task, which could get automated.
So the VS-Code extension should be able to take such a list and create the related rst/md code for me. Example:
.. tool:: Sphinx
:id: SPHINX
.. feature:: Build HTML
:id: SOME_HASH_1
.. error:: Directive not found
:id: SOME_HASH_2
:links: SOME_HASH_1
So also some configuration is needed:
Sphinx-Needs type for each level
Nested objects (as part of parent content) or always standalone objects?
I often use nested lists to define and discuss some content. Like a tool->feature->error list:
When everything is discussed, this list gets transformed by hand to Sphinx-Needs objects. This is an annoying and stupid task, which could get automated.
So the VS-Code extension should be able to take such a list and create the related rst/md code for me. Example:
So also some configuration is needed: