Cannot link against items in wasm_bindgen_futures from third-party crates

[allsey87]

Summary

I am writing the documentation for my crate and trying to link against items inside of wasm_bindgen_future without much success. For example, when I try to link against wasm_bindgen_future::spawn_local:

//! See [`wasm_bindgen_future::spawn_local`]

the output just renders as [wasm_bindgen_future::spawn_local] instead of wasm_bindgen_future::spawn_local. cargo doc produces no warning or errors, however, I can see that the item is highlighted as a function (in vscode with rust analyzer) when it exactly matches. This seems to suggest that vscode can find the item being referenced while rustdoc cannot.

Additional Details

I have the following configuration under .cargo/config.toml. Not sure if this is relevant...

[build]
target = "wasm32-unknown-unknown"

[target.wasm32-unknown-unknown]
runner = 'wasm-bindgen-test-runner'

[daxpedda]

Could you share your Cargo.toml?

[daxpedda]

The issue is that cargo doc doesn't use dev-dependencies.
If you add wasm-bindgen-test to dependencies it will work. Obviously this is most likely undesirable.

I remember there being an issue about this in the Rust repositories, but I can't seem to find it.

[allsey87]

I am a little bit lost... why would the dependency on wasm-bindgen-test have an influence over whether wasm_bindgen_future::spawn_local is visible to cargo doc?

[daxpedda]

Ah, apologies, I think I mixed up some issues I was responding to at the same time!

I noticed that you were writing wasm_bindgen_future everywhere, the "s" is missing at the end.
Though its there in your repo, so I assume you just misspelled it in this issue.

In any case, this is most likely a Rustdoc issue then.

[allsey87]

No problem, and sorry about the typo! It might indeed be a Rustdoc issue but it seems to be only local since when I publish the crate the links render correctly on docs.rs