This is handled by the rocsphinx Sphinx extension, a fork of mozsphinx. It
differs from mozsphinx in a key way: The document paths are not extracted from
moz.build files, they are set in `docs/config.yml` in the `doc_trees` mapping.
This was done to keep rocsphinx from importing code (mozbuild) that is in
the Gecko tree. When ReadTheDocs builds the documentation, it only has the
Comm source to work with.
The config file also has a `python_package_dirs` list structure which can be
used in the future to include Python documentation for comm_taskgraph among
other things.
Differential Revision: https://phabricator.services.mozilla.com/D221054
--HG--
extra : amend_source : a4bec120d48e93545ed5e276351f548b5d6f3349
It turns out that sphinx_js doesn't really do anything with `jsdoc_config_path`
except pass it along to jsdoc itself, which will happily execute a javascript
module. This saves having to write out a new JSON file in the source directory
when building docs.
Differential Revision: https://phabricator.services.mozilla.com/D208786
--HG--
rename : docs/jsdoc.conf.json => docs/jsdoc.conf.js
extra : amend_source : 71be7a74bfbbad14817e39ea8aeda2db0358a069
extra : absorb_source : 967dcb9111a372a93aba2b06271f75fa3ff95dd5
Heather Ellsworth
Rob Lemley
Daniel Darnell