You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 28, 2022. It is now read-only.
While developing, I usually use the --no-deps option to cargo doc. That usually means that when using cargo docserver, http:://myhostname:4000 redirects me to a blank "not found" page, because by default it seems to choose the alphabetically lowest ordered crate from within all of my dependencies. Obviously, those dependencies' docs won't be present if I use --no-deps. Worse, cargo docserver seems to include dev-dependencies in that list. Those aren't present even when not using --no-deps. Instead, cargo docserver should be default redirect to the current directory's crate, the first crate whose documentation is found, or a landing page showing all available crates.
While developing, I usually use the
--no-depsoption tocargo doc. That usually means that when usingcargo docserver, http:://myhostname:4000 redirects me to a blank "not found" page, because by default it seems to choose the alphabetically lowest ordered crate from within all of my dependencies. Obviously, those dependencies' docs won't be present if I use--no-deps. Worse, cargo docserver seems to include dev-dependencies in that list. Those aren't present even when not using--no-deps. Instead, cargo docserver should be default redirect to the current directory's crate, the first crate whose documentation is found, or a landing page showing all available crates.