Skip to content

Avoid wrapping inline code spans#61

Merged
leynos merged 2 commits intomainfrom
codex/adjust-wrapping-algorithm-for-backtick-strings
Jul 14, 2025
Merged

Avoid wrapping inline code spans#61
leynos merged 2 commits intomainfrom
codex/adjust-wrapping-algorithm-for-backtick-strings

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jul 14, 2025

Summary

  • avoid wrapping in wrap_text within backtick code spans
  • add regression test to cover the new wrapping behaviour

Testing

  • cargo +nightly-2025-06-10 fmt --all
  • cargo clippy -- -D warnings
  • RUSTFLAGS="-D warnings" cargo test
  • markdownlint docs
  • nixie docs

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

Summary by Sourcery

Preserve inline code spans during text wrapping by protecting spaces inside backtick-delimited segments from being split and restoring them after wrapping

Bug Fixes:

  • Prevent wrapping logic from splitting inline code spans across lines

Enhancements:

  • Introduce replace_spaces_in_code to replace spaces within backtick code spans with non-breaking spaces before wrapping
  • Integrate code span protection into flush_paragraph by wrapping on protected text and restoring spaces afterward

Tests:

  • Add regression test to verify inline code spans remain intact after wrapping

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jul 14, 2025

Reviewer's Guide

Introduce a pre-processing step that masks spaces inside backtick-delimited code spans with non-breaking spaces to prevent internal wrapping, integrate this into the paragraph flush routine, and add a regression test to verify the behavior.

Class diagram for new code span handling in text wrapping

classDiagram
    class flush_paragraph {
        +flush_paragraph(out: &mut Vec<String>, buf: &[(String, bool)], indent: &str, width: usize)
    }
    class replace_spaces_in_code {
        +replace_spaces_in_code(text: &str) String
    }
    flush_paragraph --> replace_spaces_in_code : calls
Loading

File-Level Changes

Change Details Files
Mask spaces in inline code spans
  • Implement replace_spaces_in_code that scans for backtick sequences, tracks entry/exit of code spans, and replaces spaces with NBSPs
  • Count consecutive backticks to handle multi-backtick spans correctly
src/lib.rs
Integrate masking into flush_paragraph
  • Invoke replace_spaces_in_code on each segment before wrapping
  • After fill(), restore original spaces by replacing NBSPs back in both hard-break and final flush paths
src/lib.rs
Add regression test for code-span wrapping
  • Add wrap_text_preserves_code_spans in mod tests to ensure inline code isn’t split across wrapped lines
src/lib.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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 14, 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 5 minutes and 8 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 e7aa39f and 2b913eb.

📒 Files selected for processing (1)
  • src/lib.rs (4 hunks)

Summary by CodeRabbit

  • New Features

    • Improved text wrapping to preserve the integrity of inline code spans, ensuring spaces within code are not split across lines.
  • Tests

    • Added a test to verify that text wrapping does not break spaces inside inline code spans.

Walkthrough

Introduce a helper function to replace spaces within inline code spans with non-breaking spaces, ensuring code spans are not split during text wrapping. Update the paragraph flushing logic to apply this transformation before and after wrapping. Add a test verifying that code spans remain intact after wrapping.

Changes

File(s) Change Summary
src/lib.rs Add replace_spaces_in_code helper. Update flush_paragraph to use it before/after wrapping.
src/lib.rs (test) Add test wrap_text_preserves_code_spans for code span integrity during wrapping.

Possibly related PRs

Poem

In code spans, spaces must not flee,
So non-breaking bonds set them free.
With wrapping now wise,
No split will arise—
Inline code stays whole, as it should be!

Keep calm and wrap on!

✨ 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/adjust-wrapping-algorithm-for-backtick-strings

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

  • There’s duplicate logic in both the hard-break and final wrap branches where you call replace_spaces_in_code, fill, then restore spaces—consider extracting that into a small helper to DRY up the code.
  • The replace_spaces_in_code function could use a doc comment or a more descriptive name (e.g. protect_code_span_spaces) to make its purpose and behavior clearer.
  • The manual backtick counting/state logic may miss some edge cases (e.g. varying backtick delimiters or backticks inside code); consider adding targeted tests or using a regex-based split to simplify and harden this logic.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- There’s duplicate logic in both the hard-break and final wrap branches where you call replace_spaces_in_code, fill, then restore spaces—consider extracting that into a small helper to DRY up the code.
- The replace_spaces_in_code function could use a doc comment or a more descriptive name (e.g. protect_code_span_spaces) to make its purpose and behavior clearer.
- The manual backtick counting/state logic may miss some edge cases (e.g. varying backtick delimiters or backticks inside code); consider adding targeted tests or using a regex-based split to simplify and harden this logic.

## Individual Comments

### Comment 1
<location> `src/lib.rs:258` </location>
<code_context>
 /// wrapped lines to the output vector with the given indentation. Lines are wrapped to the
 /// specified width minus the indentation length. Hard breaks in the buffer force a line break at
 /// that point.
+fn replace_spaces_in_code(text: &str) -> String {
+    let mut out = String::with_capacity(text.len());
+    let mut chars = text.chars().peekable();
</code_context>

<issue_to_address>
Consider refactoring the code to use a regex-based helper for code span handling and a single wrap function to simplify logic.

```suggestion
You can simplify the “protect‐fill‐restore” logic by splitting out a small helper and using a regex to find code spans instead of manual backtick counting. For example:

```rust
use regex::Regex;

// Protect only spaces inside inline code spans:
fn protect_code_spaces(text: &str) -> String {
    // this matches any sequence of backticks + content + same number of backticks
    lazy_static::lazy_static! {
        static ref CODE_RX: Regex = Regex::new(r"(`+[^`]*`+)").unwrap();
    }
    CODE_RX.replace_all(text, |caps: &regex::Captures| {
        caps[0].replace(' ', "\u{00A0}")
    }).into_owned()
}

// Single helper for wrap-and-restore:
fn wrap_segment(
    seg: &str,
    indent: &str,
    width: usize,
    out: &mut Vec<String>,
) {
    let opts = Options::new(width - indent.len())
        .word_splitter(WordSplitter::NoHyphenation);
    let protected = protect_code_spaces(seg);
    for line in fill(&protected, &opts).lines() {
        // restore NBSP → space only after wrapping
        let restored = line.replace('\u{00A0}', " ");
        out.push(format!("{indent}{restored}"));
    }
}

// Then flush_paragraph becomes:
fn flush_paragraph(
    out: &mut Vec<String>,
    buf: &[(String, bool)],
    indent: &str,
    width: usize,
) {
    if buf.is_empty() { return; }

    let mut seg = String::new();
    for (text, hard) in buf {
        if !seg.is_empty() {
            seg.push(' ');
        }
        seg.push_str(text);
        if *hard {
            wrap_segment(&seg, indent, width, out);
            seg.clear();
        }
    }
    if !seg.is_empty() {
        wrap_segment(&seg, indent, width, out);
    }
}
```

This

- removes manual iterator/peek logic,
- handles arbitrary backtick spans via regex,
- factors out the duplicate wrap loops into `wrap_segment`.

</issue_to_address>

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.

Comment thread src/lib.rs Outdated
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: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1320a9d and e7aa39f.

📒 Files selected for processing (1)
  • src/lib.rs (3 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.rs

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • AGENTS.md

⚙️ CodeRabbit Configuration File

⏰ Context from checks skipped due to timeout of 240000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build-test
🔇 Additional comments (2)
src/lib.rs (2)

303-307: Approve the protected wrapping implementation.

The logic correctly protects code spans before wrapping and restores normal spaces afterwards. The two-step process ensures code spans remain intact during text wrapping whilst preserving original formatting in the output.


313-317: Approve the consistent protection pattern.

The same protection logic is correctly applied to the remaining segment after hard breaks, maintaining consistency in code span handling throughout the paragraph flushing process.

Comment thread src/lib.rs
Comment thread src/lib.rs Outdated
@leynos leynos merged commit 951071d into main Jul 14, 2025
2 checks passed
@leynos leynos deleted the codex/adjust-wrapping-algorithm-for-backtick-strings branch July 14, 2025 17:27
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