-
Notifications
You must be signed in to change notification settings - Fork 8
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
:literalref:
should be able to work like :ref:
#47
Comments
|
We have a lot of cases where we want to link to a reference that refers to a YAML key, a filename, a charmcraft command, etc., that should be treated as literals as well. A nice example of the first three listed is at https://canonical-charmcraft.readthedocs-hosted.com/en/stable/reference/files/charmcraft-yaml-file/:
|
I see, that's fair. I'm not sure when we'll be able to give this the attention it deserves, but for the moment, the combo-roles extension can be used to combine the |
The combo-roles site is down for me. The repo is here: https://github.com/sphinx-notes/comboroles |
Resolve erroneous link warnings affecting literalref directives. Sphinx-lint will no longer check for spaces before angle brackets (` <>`) or underscores after graves (`_). The root cause is a bug in our implementation of literalref: canonical/canonical-sphinx-extensions#47
Resolve erroneous link warnings affecting literalref directives. Sphinx-lint will no longer check for spaces before angle brackets (` <>`) or underscores after graves (`_). The root cause is a bug in our implementation of literalref: canonical/canonical-sphinx-extensions#47
Currently using
literalref
is a bit unintuitive, as it can only work like standard reStructuredText links. It should also be able to reference labels like:ref:
.The text was updated successfully, but these errors were encountered: