Skip to content

Implement unified response and error types#128

Merged
leynos merged 5 commits intomainfrom
codex/unify-response-and-wireframeerror-types
Jun 25, 2025
Merged

Implement unified response and error types#128
leynos merged 5 commits intomainfrom
codex/unify-response-and-wireframeerror-types

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jun 24, 2025

Summary

  • implement Response and WireframeError enums
  • re-export new types from the crate root
  • mark roadmap item as complete
  • disable MD056 for roadmap table

Testing

  • make fmt
  • make lint
  • make test
  • markdownlint *.md **/*.md
  • mdformat-all

https://chatgpt.com/codex/tasks/task_e_685b239b2868832296e4ac7b899c82cc

Summary by Sourcery

Implement unified response and error types, expose them at the crate root, and update documentation to reflect and format these additions.

New Features:

  • Introduce Response<F, E> enum with Single, Vec, Stream, and Empty variants and a FrameStream alias for streaming frames
  • Add WireframeError enum to distinguish I/O and protocol errors with conversion helpers

Enhancements:

  • Re-export Response, WireframeError, and FrameStream at the crate root for convenient access

Documentation:

  • Mark unified Response and WireframeError types as complete in the roadmaps, disable MD013/MD056 lint rules, and adjust table formatting for readability

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jun 24, 2025

Reviewer's Guide

This PR introduces a unified response and error handling model by adding the Response and WireframeError enums (with convenience impls and type alias), re-exports them at the crate root, and updates the project documentation to disable a lint rule and mark the roadmap item as complete.

File-Level Changes

Change Details Files
Add unified Response enum and FrameStream alias
  • Define FrameStream as a boxed, pinned Stream alias
  • Implement Response enum with Single, Vec, Stream, and Empty variants
  • Provide Debug impl for Response
  • Add From and From<Vec> conversions for Response
src/response.rs
Introduce WireframeError enum for I/O and protocol errors
  • Define WireframeError with Io and Protocol variants
  • Implement From conversion and from_io constructor
src/response.rs
Re-export response types from the crate root
  • Add pub mod response declaration
  • Expose FrameStream, Response, and WireframeError via pub use
src/lib.rs
Update documentation roadmap and disable MD056 lint
  • Insert markdownlint disable comment in detailed roadmap
  • Adjust table formatting for consistency
  • Mark unified Response and WireframeError task as complete
docs/wireframe-1-0-detailed-development-roadmap.md
docs/asynchronous-outbound-messaging-roadmap.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on 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 issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on 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 dismiss on 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 review to 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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 24, 2025

Warning

Rate limit exceeded

@leynos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 28 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 15b2e64 and 1c586cf.

📒 Files selected for processing (2)
  • docs/wireframe-1-0-detailed-development-roadmap.md (2 hunks)
  • src/response.rs (1 hunks)

Summary by CodeRabbit

  • New Features

    • Introduced new response and error types for protocol handler outputs, including support for single, multiple, streamed, or empty responses, and unified error handling.
    • Made new response-related types directly accessible to users.
  • Documentation

    • Updated roadmaps to reflect completed tasks and improved formatting for clarity and linting compliance.
    • Made minor formatting adjustments for better readability.

Summary by CodeRabbit

  • New Features
    • Introduced new response and error types for handling protocol operations, including unified response handling and error categorisation.
    • Made response types and error handling utilities directly accessible for easier integration.
  • Documentation
    • Improved roadmap documentation with clearer formatting and updated task completion status for unified response and error types.

Walkthrough

A new response module was introduced, defining unified response and error types for handler outputs in the wireframe protocol. Key types—FrameStream, Response, and WireframeError—are now publicly re-exported at the crate root. Related documentation was updated to reflect the completion of this unification, and markdown formatting improvements were made.

Changes

File(s) Change Summary
src/response.rs New module defining FrameStream, Response, and WireframeError types, including error handling and conversion.
src/lib.rs Added public response module and re-exported FrameStream, Response, and WireframeError at crate root.
docs/asynchronous-outbound-messaging-roadmap.md Marked the "Unified Response<F, E> and WireframeError<E> types" checklist item as complete.
docs/wireframe-1-0-detailed-development-roadmap.md Improved markdown table formatting and added markdownlint disable comment; no content changes.
docs/asynchronous-outbound-messaging-design.md Minor formatting adjustment to line break in Implementation Status section; no content change.

Sequence Diagram(s)

sequenceDiagram
    participant Handler
    participant Response
    participant Client

    Handler->>Response: Produce Response<F, E> (Single, Vec, Stream, or Empty)
    Response-->>Client: Deliver frames or error (WireframeError<E>)
Loading

Suggested reviewers

  • codescene-delta-analysis

Poem

A rabbit hopped to wireframe’s core,
With responses unified, errors galore—
Now streams and frames are neatly tied,
In enums where bugs can’t hide!
Docs are checked, tables aligned,
This bunny’s code is well-defined.
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch codex/unify-response-and-wireframeerror-types

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @leynos - I've reviewed your changes - here's some feedback:

  • Consider deriving Debug (and potentially Clone/PartialEq) on Response and WireframeError to improve logging and testing ergonomics.
  • Add From and From<Vec> implementations for Response<F, E> so handlers can return single or multiple frames without explicit wrapping.
  • Implement a From for WireframeError (in addition to the existing std::io::Error conversion) to streamline propagating protocol errors.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Consider deriving Debug (and potentially Clone/PartialEq) on Response and WireframeError to improve logging and testing ergonomics.
- Add From<F> and From<Vec<F>> implementations for Response<F, E> so handlers can return single or multiple frames without explicit wrapping.
- Implement a From<E> for WireframeError<E> (in addition to the existing std::io::Error conversion) to streamline propagating protocol errors.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jun 25, 2025

@sourcery-ai review

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @leynos - I've reviewed your changes and found some issues that need to be addressed.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@leynos leynos merged commit 2c98d64 into main Jun 25, 2025
5 checks passed
@leynos leynos deleted the codex/unify-response-and-wireframeerror-types branch June 25, 2025 00:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant