Aliasing latest

[passcod]

It would be nice to have aliasing (through the use of, say, symlinks) for the latest version, so we could point the README of a project to https://crates.fyi/crates/cratename/latest/.

[onur]

This is the first thing in my TODO. I am trying to catch crates.io-index atm. There are 30 crates in que. Building google-* crates taking too much time.

[passcod]

As an addendum, although I'm not sure of the use, version aliasing like 3 -> latest 3.x.y version and 3.2 -> latest 3.2.x could be useful for libraries that maintain multiple branches/versions.

[icorderi]

Hey, was about to ask for this feature.
Bump it up! +1

@passcod makes an interesting point.@onur have you thought about a .cratesfyi configuration file where we can say 3.x.y = branch/name. That would address @passcod requirement and gives people the ability to control aliases from their own repo.

[passcod]

@icorderi I believe crates.fyi builds from crates.io, not github, so the concept of branch names doesn't apply.

[reem]

Yeah I would love a "latest" tag, would be really nice to just be able to stick a latest docs link in the README of every project and never worry about it again.

[onur]

Adding sources other than crates.io is in my TODO but I am planning to support only crates released into crates.io for now. cratesfyi may fetch (or listen) crate repository and generate doc from a specific branch in future.

And for the "latest" tag, like I said in #2 this project is changed alot, whole directory structure and htmls are different than currently available in crates.fyi. Build machine is using an old version of cratesfyi. I am planning to host docs in a subdomain like rustdoc.crates.fyi. And planning to add a redirector to latest version of crate. Let's say you wanted to access documentation of latest version of "cargo" crate, rustdoc.crates.fyi/cargo will redirect to latest version of crate documentation.