We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the Python domain, one can use code like the following:
.. py:function:: spam(eggs) ham(eggs) Spam or ham the foo.
With this, the py:function will be in the objects.inv file which is generated when the documentation is built:
py:function
objects.inv
~> python -m sphinx.ext.intersphinx ./build/html/objects.inv py:function target index.html#target ...
The same happens with C++ code wh
However, when the Sphinx Bazel domain is used, nothing is outputted to objects.inv.
When an object is referenced in objects.inv, there are multiple features available.
The one that I am interested in is to have the Bazel rules referenced in a Dash index using doc2dash.
The text was updated successfully, but these errors were encountered:
I believe that this means implementing get_objects in BazelDomain.
get_objects
BazelDomain
Sorry, something went wrong.
No branches or pull requests
With the Python domain, one can use code like the following:
With this, the
py:function
will be in theobjects.inv
file which is generated when the documentation is built:The same happens with C++ code wh
However, when the Sphinx Bazel domain is used, nothing is outputted to
objects.inv
.When an object is referenced in
objects.inv
, there are multiple features available.The one that I am interested in is to have the Bazel rules referenced in a Dash index using doc2dash.
The text was updated successfully, but these errors were encountered: