Replies: 1 comment 3 replies
-
I'm not sure I agree with that proposal unless we can be absolutely sure that both pages always show the exact same version. That would require us to perform the "default version" resolution on the server side and publish it on the API. That is certainly a possibility, but nothing we are currently doing. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Current behavior: the "latest" revision of a crate page, e.g. https://crates.io/crates/ureq, shows a link to docs.rs with an explicitly versioned URL, e.g. docs.rs/ureq/2.5.0. Since last year, docs.rs offers a page that will always show the latest version of docs: https://docs.rs/ureq/latest/ureq/. There's also a longstanding redirect from https://docs.rs/ureq that now goes to /latest/. The redirect is preferable because the linking page doesn't have to worry about crate name vs package name distinctions (
-
vs_
, usually).The purpose of the
/latest/
URL is to have a consistent URL for search engines to assign rank to, to avoid searching engines linking to outdated crate versions.To that end, it would be helpful if crates.io would link to
docs.rs/<crate>
instead ofdocs.rs/<crate>/<version
, specifically in the case where the user is not on a specifically versioned page on crates.io.Beta Was this translation helpful? Give feedback.
All reactions