While waiting for a book PR to pass CI on main, I noticed cargo doc is generating API docs for all dependencies.
This is really nice to have as a local dev, and it's also good to ensure that all of the API docs in our repo pass errors/warnings, but for third party dependencies, it would be nice to cache them or skip them.
Different wishlist is to include hosted API docs, which would include these. That could either rely on caching, or be a separate CI pipe outside of merges to main. (I still want our API docs to be a main-merge requirement in CI, though.)
While waiting for a book PR to pass CI on main, I noticed
cargo docis generating API docs for all dependencies.This is really nice to have as a local dev, and it's also good to ensure that all of the API docs in our repo pass errors/warnings, but for third party dependencies, it would be nice to cache them or skip them.
Different wishlist is to include hosted API docs, which would include these. That could either rely on caching, or be a separate CI pipe outside of merges to
main. (I still want our API docs to be amain-merge requirement in CI, though.)