139139//!
140140//! ## Module Overview
141141//!
142- //! - [`task`]: The [`Task`] trait — single `run()` method
143- //! - [`node`]: The [`Node`] trait — three-phase lifecycle with retry via [`TaskConfig`]
142+ //! - [`mod@ task`]: The [`Task`] trait — single `run()` method
143+ //! - [`mod@ node`]: The [`Node`] trait — three-phase lifecycle with retry via [`TaskConfig`]
144144//! - [`workflow`]: [`Workflow`] — FSM orchestration with Split/Join support
145145//! - [`scheduler`] (requires `scheduler` feature): [`Scheduler`] — cron and interval scheduling
146- //! - [`resource`]: [`Resource`] trait and [`Resources`] dictionary — lifecycle-aware resource management
146+ //! - [`mod@ resource`]: [`Resource`] trait and [`Resources`] dictionary — lifecycle-aware resource management
147147//! - [`store`]: [`MemoryStore`] and the [`KeyValueStore`] trait — [`MemoryStore`] implements [`Resource`]
148148//! - [`error`]: [`CanoError`] variants and the [`CanoResult`] alias
149149//!
@@ -181,7 +181,7 @@ pub use scheduler::{FlowInfo, Scheduler};
181181/// to rewrite `async fn` methods into ones returning
182182/// `Pin<Box<dyn Future<Output = ...> + Send + 'async_trait>>`.
183183///
184- /// Functionally identical to [`node`] and [`resource`]; the separate name makes
184+ /// Functionally identical to [`macro@ node`] and [`macro@ resource`]; the separate name makes
185185/// `#[cano::task]` self-documenting at impl sites. The implementation lives in
186186/// the [`cano-macros`] sibling crate.
187187///
@@ -190,19 +190,19 @@ pub use cano_macros::task;
190190
191191/// Attribute macro applied to the `Node` trait definition and `impl Node` blocks.
192192///
193- /// See [`task`] for the rewrite shape; this macro is functionally identical and
193+ /// See [`macro@ task`] for the rewrite shape; this macro is functionally identical and
194194/// differs only in name.
195195pub use cano_macros:: node;
196196
197197/// Attribute macro applied to the `Resource` trait definition and `impl Resource` blocks.
198198///
199- /// See [`task`] for the rewrite shape; this macro is functionally identical and
199+ /// See [`macro@ task`] for the rewrite shape; this macro is functionally identical and
200200/// differs only in name.
201201pub use cano_macros:: resource;
202202
203203/// Derive macro that generates a `from_resources` associated function for a struct.
204204///
205- /// See [`cano_macros::derive_from_resources `] for the full specification. Each
205+ /// See [`FromResources `] for the full specification. Each
206206/// field must be `Arc<T>`; annotate it with `#[res("key")]` or
207207/// `#[res(EnumKey::Variant)]`.
208208pub use cano_macros:: FromResources ;
@@ -213,9 +213,8 @@ pub use cano_macros::FromResources;
213213/// but derived directly from the struct definition. The trait's no-op `setup`
214214/// and `teardown` defaults take effect automatically.
215215///
216- /// In the prelude, this is exported as [`Resource`](crate::prelude::Resource)
217- /// alongside the trait of the same name — Rust's separate macro and type
218- /// namespaces let them coexist.
216+ /// In the prelude, this is exported as [`Resource`] alongside the trait of the
217+ /// same name — Rust's separate macro and type namespaces let them coexist.
219218pub use cano_macros:: Resource ;
220219
221220// Convenience re-exports for common patterns
0 commit comments