From b8e19a31b287714f3f8cea1830a05fe6e5dd80b0 Mon Sep 17 00:00:00 2001 From: atlas Date: Sun, 16 Aug 2026 13:52:43 +0200 Subject: [PATCH] docs(swarm-queue-client): qualify the status-bucket intra-doc link MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit An unqualified `[`open_or_create`]` in the module-level doc does not resolve once the `kv` feature is on, which is the only configuration where the module is compiled at all — so `docs-rustdoc` failed in CI while a default-feature `cargo doc` passed locally. Measured both ways: kv off documents clean, kv on errors `no item named open_or_create in scope`. Qualifying the path fixes it without widening any visibility, which is the rule that check exists to protect. --- swarm-queue-client/src/status.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/swarm-queue-client/src/status.rs b/swarm-queue-client/src/status.rs index 0a38d7d7..1c8689b2 100644 --- a/swarm-queue-client/src/status.rs +++ b/swarm-queue-client/src/status.rs @@ -7,7 +7,7 @@ //! repeated across crates is an agreement nothing checks.** //! //! The name is the obvious half. The sharper half is the *config*: both -//! ends open the bucket with [`open_or_create`], because either may +//! ends open the bucket with [`crate::status::open_or_create`], because either may //! arrive first on a fresh swarm and neither can assume the other has //! run. If the two ends passed different `Config`s, whichever created it //! would win and the other's `get_key_value` would succeed against a