Repository navigation
docs(api): add executable observer usage example - #490
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 18 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
f3b3ca3 to
1189ba4
Compare
8ea8e86 to
9899e9f
Compare
Library callers need a checked example of configuring progress reporting and clearing it without relying on internal test helpers.
9899e9f to
d32e1aa
Compare
|
@codex review |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Library callers need a checked example of configuring progress reporting without internal helpers. Add an executable public API example showing AfterPush handling and disabling the observer.
This example uses APIs already on main and can merge independently of the integration-test stack.
Validation: workspace tests including the new doctest, Clippy with warnings denied, formatting and diff checks pass.