-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use :envvar: to refer to variables. (was: Updated to Sphinx 1.3 to allow using :any: to reference vars) #140
Conversation
Refer to the [Sphinx documentation about `:any:`](http://www.sphinx-doc.org/en/stable/markup/inline.html#role-any) `:any:` can be used in Sphinx to reference variables. Example: ```YAML ferm__enabled: True ferm__flush: '{{ ferm__enabled | bool }}' ``` When using this, we might need to adjust sections names. Example: ```reStructuredText .. _ferm_input_list: ferm_input_list --------------- ``` could be changed to: ```reStructuredText .. _ferm_detailed_input_list: ferm_input_list --------------- ``` 1.3.4 has been chosen because it is the current version in [jessie-backports](https://packages.debian.org/jessie-backports/python-sphinx).
Actually. I think we should add a proper namespace for sections.
.. _ferm__section_detailed_input_list:
ferm_input_list
--------------- |
So far there is only one "target" for each default variable with detailed documentation, so for example with:
Everything should be covered. Do you think that there could be more targets? |
Actually, I do. The reason of this PR was to enable the use of the
Check the http://docs.debops.org/en/latest/ansible/roles/ansible-apt_install/docs/changelog.html#v0-1-1 in which I made use of this feature. |
Related to debops/docs#140
OK, I presume that works. However, some of the variable names are long already an writing a nice paragraph that looks OK in the file is sometimes hard, I wouldn't want to add
What do you think? |
@drybjed Nice 👍 Lets go with that. |
OK. |
@ganto has read the Sphinx documentation more carefully then I did and uses I think |
Refer to the Sphinx documentation about
:envvar:
.:envvar:
can be used in Sphinx to reference variables. Example:When using this, we might need to adjust sections names. Example:
could be changed to:
to avoid duplicates. The good thing is that Sphinx as of 1.3.4 warns when referencing a label for which multiple targets exist.
1.3.4 has been chosen because it is the current version in jessie-backports.
Edited: Changed
:any:
to:envvar:
. See comment