📝 Add docstrings to codex/standardise-trait-definitions-for-frameprocessor#10
Conversation
…cessor` (#9) Docstrings generation was requested by @leynos. * #8 (comment) The following files were modified: * `src/extractor.rs` * `src/middleware.rs` * `src/server.rs` Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
…cessor` Docstrings generation was requested by @leynos. * #8 (comment) The following files were modified: * `src/extractor.rs` * `src/middleware.rs` * `src/server.rs`
Reviewer's GuideThis PR adds comprehensive docstrings and illustrative examples to key public methods in extractor.rs, server.rs, and middleware.rs to improve clarity and documentation consistency. Class diagram for
|
| Change | Details | Files |
|---|---|---|
| Enhanced docstrings for payload and shared state utilities |
|
src/extractor.rs |
| Documented server builder’s worker configuration |
|
src/server.rs |
| Added docstrings to middleware Next helper |
|
src/middleware.rs |
Tips and commands
Interacting with Sourcery
- Trigger a new review: Comment
@sourcery-ai reviewon the pull request. - Continue discussions: Reply directly to Sourcery's review comments.
- Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with@sourcery-ai issueto create an issue from it. - Generate a pull request title: Write
@sourcery-aianywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai titleon the pull request to (re-)generate the title at any time. - Generate a pull request summary: Write
@sourcery-ai summaryanywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment@sourcery-ai summaryon the pull request to
(re-)generate the summary at any time. - Generate reviewer's guide: Comment
@sourcery-ai guideon the pull
request to (re-)generate the reviewer's guide at any time. - Resolve all Sourcery comments: Comment
@sourcery-ai resolveon the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore. - Dismiss all Sourcery reviews: Comment
@sourcery-ai dismisson the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai reviewto trigger a new review!
Customizing Your Experience
Access your dashboard to:
- Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others. - Change the review language.
- Add, remove or edit custom review instructions.
- Adjust other review settings.
Getting Help
- Contact our support team for questions or feedback.
- Visit our documentation for detailed guides and information.
- Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.
|
Important Review skippedCodeRabbit bot authored PR detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
…call_streaming - Extend Packet trait with is_stream_terminator method for end-of-stream detection. - Introduce ResponseStream type implementing futures::Stream to consume multi-frame server responses. - Add call_streaming and receive_streaming methods on WireframeClient for high- and low-level streaming APIs. - Implement correlation ID validation and terminator frame handling in streamed responses. - Provide unit and BDD tests covering normal, empty, mismatch, and disconnect scenarios. - Update docs: multi-packet design, user guide with streaming client usage, and roadmap. This completes design goal G5 by enabling clients to asynchronously consume streaming and multi-packet responses with proper correlation and terminator semantics, propagating back-pressure naturally through TCP. No breaking API changes; all additions are backward-compatible. Closes #10.3.1. Co-authored-by: devboxerhub[bot] <devboxerhub[bot]@users.noreply.github.com>
Docstrings generation was requested by @leynos.
The following files were modified:
src/extractor.rssrc/middleware.rssrc/server.rsThese file types are not supported
Cargo.tomldocs/roadmap.mddocs/rust-binary-router-library-design.mdℹ️ Note
Summary by Sourcery
Add comprehensive docstrings with usage examples to core methods and types across extractor, middleware, and server modules
Enhancements: