Skip to content
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

Open
agausmann opened this issue Oct 15, 2020 · 7 comments
Open

Support for intra-doc links #55

agausmann opened this issue Oct 15, 2020 · 7 comments

Comments

@agausmann
Copy link

agausmann commented Oct 15, 2020

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 at docs.rs or wherever else the API documentation is hosted.

@zbraniecki
Copy link

It would be great to have an ability to customize the docs path (instead of hardcoding docs.rs) - we use live docs in a custom github pages location and would prefer to link our readme to that.

@agausmann
Copy link
Author

agausmann commented Nov 8, 2020

or wherever else the API documentation is hosted.

Maybe via a command-line option, or it can read it from the Cargo.toml parameter. However I agree it would make more sense to link to docs generated from the latest commit, if they are available, instead of the docs URL in the manifest.

@zicklag
Copy link

zicklag commented May 11, 2021

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.

@LPGhatguy
Copy link

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 thunderdome: https://github.com/LPGhatguy/thunderdome/blob/21606a1172521772dfae79d9a247e6ab12a641b0/README.tpl#L5-L6

@orium
Copy link

orium commented Nov 19, 2021

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 :)

@Manishearth
Copy link

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 # lines from rust code samples.

@orium
Copy link

orium commented Sep 27, 2022

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 # in rust code. And it also tags the markdown code block as rust if that was not the case (even if it is just tagged as should_panic or no_run or all the other stuff rustdoc recognizes as rust code).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants