fix: use absolute links for inherited items #105
Conversation
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
We've reviewed this pull request using the Sourcery rules engine. If you would also like our AI-powered code review then let us know.
|
Hi, it is a long known problem. Past versions of MkDocs did not support absolute links to files. I found it, but I have not implemented it yet. A deeper look into the project and updating more generated files is needed. If you want to look at it, add I'll get to it in about a month at the earliest.
I will be happy to accept your PR. I have tested your PR, but for me, it returns the same Werning as previously. |
These warnings are gone now. They were a bit unrelated as they're from the snippet generation. Since all generated files for one project are on a single level, it's fine to set the |
Nerixyz
force-pushed
the
fix/inherited-links
branch
from
d036f4a
to
bced434
Compare
|
Thank you for your PR. I have tested it, and everything works well 😍 |
Hello @JakubAndrysek , Thanks for this wonderful plugin. I am trying to render output of mkdoxy through dev container. I want to store and see the output files in a custom folder, tried adding My mkdoxy config looks like this -
DOXYFILE --> Surprisingly, when i do
FYI Also If even after this works, is the addition of output files in nav section in mkdocs.yml a manual process? will the following work in my case? Thanks!! Any ideas to resolve this? Created an issue for this - #108 |
When compiling the documentation in this repository, you get a bunch of warnings about unknown links:
This PR fixes this by using absolute links when rendering inherited items or items embedded on other pages.
Btw, is there a way to see the generated markdown files? Or rather, where can I see them?