Add regression test for long inline code item

[leynos]

Summary

• add test to ensure long inline code spans with trailing punctuation are not split

Testing

• make fmt
• make lint
• make test

---

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

Summary by Sourcery

Tests:

• Add regression test to ensure long inline code spans with trailing punctuation are not split across lines.

[sourcery-ai]

Reviewer's Guide

This pull request adds a regression test to ensure that long inline code spans with trailing punctuation in list items are not incorrectly split during text wrapping.

File-Level Changes

Change	Details	Files
Added a regression test to verify long inline code spans with trailing punctuation are not split during processing.	Introduced new test function to cover long inline code with trailing punctuation in list items. Checked that the output wraps the list item into four lines as expected. Asserted that the first output line ends with the expected punctuation.	tests/integration.rs

---

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

• 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.

[coderabbitai]

Warning

Rate limit exceeded

@leynos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 39 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 cb1e253 and 1440c69.

📒 Files selected for processing (1)

• tests/integration.rs (1 hunks)

Summary by CodeRabbit

• Tests
  • Added a new integration test to verify correct wrapping of long list items containing inline code spans.

Walkthrough

Add a new integration test to verify the correct wrapping of a long list item containing an inline code span and descriptive text. Ensure the wrapped output preserves the inline code formatting and splits the item into four lines, using an existing helper for assertion.

Changes

File(s)	Change Summary
tests/integration.rs	Add test_wrap_long_inline_code_item integration test for wrapping long list items with inline code.

Sequence Diagram(s)

sequenceDiagram
    participant TestRunner
    participant process_stream
    participant assert_wrapped_list_item

    TestRunner->>process_stream: Process long list item with inline code
    process_stream-->>TestRunner: Return wrapped lines
    TestRunner->>assert_wrapped_list_item: Assert line count and prefix preservation
    assert_wrapped_list_item-->>TestRunner: Assertion result

Loading

Possibly related PRs

• Add wrap tests for bullet and numbered lists #59: Adds the assert_wrapped_list_item helper used for asserting wrapped list item behaviour.
• Add wrap boundary code tests #62: Introduces custom wrapping logic and tests for inline code spans, directly complementing this integration test.
• Avoid wrapping inline code spans #61: Modifies wrapping logic to prevent breaking inside inline code, which this test is designed to validate.

Poem

In the land of tests, a list grew long,
With code wrapped tight, where it belonged.
Four lines it split, not one more, not less,
Ensuring the output is clean—no mess!
The helper asserts, the code stands tall,
Integration complete—cheers to all!
📝✨

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/add-test-case-for-on_unhandled-method-formatting

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0edd434 and cb1e253.

📒 Files selected for processing (1)

• tests/integration.rs (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.rs

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

• AGENTS.md

⚙️ CodeRabbit Configuration File

🧬 Code Graph Analysis (1)

tests/integration.rs (2)

src/process.rs (1)

• process_stream (76-76)

tests/common/mod.rs (1)

• assert_wrapped_list_item (17-53)

[sourcery-ai]

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 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}