-
Notifications
You must be signed in to change notification settings - Fork 17
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
Intersphinx linking to properties not working #27
Comments
The same problem happens for modules. I tried with :mod: but it does not work. |
That's weird, I hadn't tried that yet. If we don't manage to resolve this soon-ish, we could put in direct URL links, pending the resolution of this issue, as a temporary working solution |
I agree. Let's see if we can get @ggarrett13's view on it in the next few days, otherwise I agree on temporarily switching to regular URL links for now |
Apologies for the late reply. I saw the original thread in #25 and saw it closed, did not see this one.
I don't think there is a solution for linking directly to a class' properties. The following approach may be a good alternative:
Where the latter is linked and former is not. |
Actually, I found this. I don't know if it works only within the same project, or if it works for linking to external projects. Give it a go, but I consider this issue closed. |
The link posted by @ggarrett13 unfortunately does not solve the issue. While the workaround for properties holds, this does not work for modules (neither |
Potentially useful material: see this comment |
As discussed in the first couple of posts in #25:
#25 (comment)
we currently have no way of using intersphinx to use links to the tudatpy API docs for class properties. This should be resolved to allow full linking between tudat-space and API docs. Since properties are usually mentioned in the context of the linked class that they belong to, this issue does not have high priority
The text was updated successfully, but these errors were encountered: