I think that "searching" for a crate is more than simply choosing one from the auto-completion drop-down. It is an important step and you want to avoid problems here. Making it too easy is missleading, I think.

[serayuzgur]

I think that "searching" for a crate is more than simply choosing one from the auto-completion drop-down. It is an important step and you want to avoid problems here. Making it too easy is missleading, I think.
I would rather have a handy fast accessible link to open the search on crates.io and lib.rs.
There is much to read about a crate than only a crate name, version and description.
I imagine this workflow:

• in cargo.toml I would try to write the name of the crate, but I don't remember it exactly:
  reader_for = ""
  Move the cursor on "" and vscode extension crates shows.
  There is no Available versions, because this name is not a crate.
  But it has new commands:
  
  The first link simply opens https://crates.io/search?q=reader_for
  The second link simply opens https://lib.rs/search?q=reader_for
  I find the crate I want reader_for_microxml, read about it and manually copy/paste the name to cargo.toml.

Now I have the correct name and version reader_for_microxml = "1.1.7".
If I go on the version number the extension opens like this:

I can:

1. open the crate.io page
   https://crates.io/crates/reader_for_microxml
2. open the lib.rs
   https://lib.rs/crates/reader_for_microxml
3. open cargo-crev reviews (still beta)
   https://bestia.dev/cargo_crev_web/crate/reader_for_microxml
4. open the current documentation:
   https://docs.rs/crate/reader_for_microxml/1.0.4
5. open the latest documentation (to see the changes):
   https://docs.rs/crate/reader_for_microxml/1.1.6

All this commands are simple URL-s. There is no need for any additional data to get or extension behaviour to modify. Very simple.

Originally posted by @LucianoBestia in #69 (comment)