Skip to content

Update roadmap with grammar fixes#27

Merged
leynos merged 2 commits intomainfrom
codex/add-new-items-to-roadmap
Jun 14, 2025
Merged

Update roadmap with grammar fixes#27
leynos merged 2 commits intomainfrom
codex/add-new-items-to-roadmap

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jun 14, 2025

Summary

  • polish connection feature bullets for consistent verbs and grammar
  • expand testing utilities bullet with an example reference

Testing

  • cargo fmt -- --check
  • cargo clippy -- -D warnings
  • RUSTFLAGS="-D warnings" cargo test
  • npx --yes markdownlint-cli2 '**/*.md'
  • nixie docs/roadmap.md

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

Summary by Sourcery

Revise the roadmap documentation to improve consistency and clarity

Documentation:

  • Polish connection feature bullets for consistent verbs and grammar
  • Expand testing utilities entry with an example reference to tests/server.rs

Summary by CodeRabbit

  • Documentation
    • Updated the roadmap to include new core library foundation tasks and developer tooling enhancements, such as connection preamble support, response serialization, connection lifecycle hooks, and testing utilities for handlers.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jun 14, 2025

Reviewer's Guide

This update refines the roadmap documentation by standardizing connection feature bullets with consistent imperative verbs and grammar, and expands the testing utilities section by adding a concrete example reference.

Flow Diagram of Additions to Project Roadmap

graph TD
    RoadmapAdditions["Additions to Roadmap Document"]

    RoadmapAdditions --> ConnectionFeatures["Connection Features Section"]
    ConnectionFeatures --> Item1["New: Add connection preamble support"]
    ConnectionFeatures --> Item2["New: Add response serialization and transmission"]
    ConnectionFeatures --> Item3["New: Add connection lifecycle hooks"]

    RoadmapAdditions --> TestingUtilities["Testing Utilities Section"]
    TestingUtilities --> Item4["New: Provide testing utilities for handlers"]
Loading

File-Level Changes

Change Details Files
Standardize and clarify connection feature bullets
  • Use imperative 'Add' verb for each connection item
  • Introduce detailed descriptions for preamble support
  • Specify encoding and framing for response serialization
  • Detail setup and teardown in connection lifecycle hooks
docs/roadmap.md
Expand testing utilities section with example reference
  • Rename bullet to 'Provide testing utilities for handlers'
  • Describe driving handlers with raw frames for unit tests
  • Reference existing examples in tests/server.rs and future crate location
docs/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 14, 2025

Walkthrough

The roadmap documentation was updated to outline new core library foundation tasks, including connection preamble support, response serialization and transmission, and connection lifecycle hooks. Additionally, a new developer tooling item was added to provide testing utilities for handlers, with references to early examples and future plans for a dedicated crate.

Changes

File(s) Change Summary
docs/roadmap.md Added new core library foundation tasks and a developer tooling item for handler testing.

Possibly related PRs

Suggested reviewers

  • codescene-delta-analysis

Poem

In the warren where roadmaps grow,
New tasks and tools now gently flow.
Preambles, hooks, and tests in hand,
The future’s mapped upon this land.
🐇 With every hop, our plans expand—
Let’s build a brighter, bunny-branded band!


🪧 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 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

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
docs/roadmap.md (2)

58-66: Ensure proper list nesting in Markdown

The descriptive lines under each “Add …” bullet are indented but lack hyphens, which can break list nesting in many Markdown renderers. Consider converting them into true sub-bullets and aligning indentation consistently. For example:

- [ ] Add connection preamble support.
-      Provide built-in parsing of a handshake preamble (e.g., Hotline's "TRTP")
-      and invoke a user-configured handler on success or failure.
+ [ ] Add connection preamble support.
+     - Provide built-in parsing of a handshake preamble (e.g., Hotline's "TRTP") and invoke a user-configured handler on success or failure.

Or split into two sub-items:

+     - Provide built-in parsing of a handshake preamble (e.g., Hotline's "TRTP").
+     - Invoke a user-configured handler on success or failure.

107-111: Convert detail lines into Markdown sub-bullets

Similarly, the notes under “Provide testing utilities for handlers.” should be proper nested list items. For example:

- [ ] Provide testing utilities for handlers.
-      Offer simple ways to drive handlers with raw frames for unit tests.
-      Early examples live in [`tests/server.rs`](../tests/server.rs); future
-      helpers may reside in a `wireframe-testing` crate.
+ [ ] Provide testing utilities for handlers.
+     - Offer simple ways to drive handlers with raw frames for unit tests.
+     - Early examples live in [`tests/server.rs`](../tests/server.rs); future helpers may reside in a `wireframe-testing` crate.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0153c73 and dd6d8b3.

📒 Files selected for processing (1)
  • docs/roadmap.md (2 hunks)

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 they look great!


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 610bfa6 into main Jun 14, 2025
3 checks passed
@leynos leynos deleted the codex/add-new-items-to-roadmap branch June 14, 2025 02:14
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