-
Notifications
You must be signed in to change notification settings - Fork 57
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
Support for intra-doc links #55
Comments
It would be great to have an ability to customize the docs path (instead of hardcoding |
Maybe via a command-line option, or it can read it from the |
An option to remove the intra-doc links would be a decent middle-ground, so that I don't have a bunch of broken API docs links in my README, but to do that accurately would require parsing the markdown as markdown instead of the simple line-based processing procedure taken currently, due to the existence of the reference-style markdown links. |
I figured out a pretty easy workaround. Stick a Markdown reference-style link in your template for all the types you refer to. This lets you refer to a specific docs.rs version or even the latest. Here's how I did this for |
cargo-rdme implements README generation and replaces intralinks with links to docs.rs: https://github.com/orium/cargo-rdme#intralinks Disclaimer: I'm the author of the crate :) |
A way to make this more pleasant without requiring too much work would be to just strip out intra doc links. Could also strip out |
Shameless plug: cargo-rdme not only generates intralinks to docs.rs, it also has a flag (or configuration file) to strip the intralinks if you so choose. It also strips out the |
Intra-doc links allow documentation authors to link to items by their path relative to the current module. It would be nice to resolve intra-doc links in the same way that
rustdoc
does, and make them point to the documentation atdocs.rs
or wherever else the API documentation is hosted.The text was updated successfully, but these errors were encountered: