Skip to content

Add optional wrapping flag#38

Merged
leynos merged 4 commits intomainfrom
codex/make-text-wrapping-optional
Jun 15, 2025
Merged

Add optional wrapping flag#38
leynos merged 4 commits intomainfrom
codex/make-text-wrapping-optional

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jun 15, 2025

Summary

  • make text wrapping opt-in via --wrap
  • document --wrap usage in README
  • add process_stream_no_wrap and rewrite_no_wrap
  • update CLI logic for the new flag
  • test CLI wrapping behaviour

Testing

  • cargo fmt
  • cargo clippy -- -D warnings
  • RUSTFLAGS="-D warnings" cargo test
  • markdownlint README.md

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

Summary by Sourcery

Add an optional wrapping flag to make text wrapping opt-in and provide no-wrap variants for processing and in-place rewriting

New Features:

  • Add --wrap CLI option to enable paragraph and list wrapping
  • Introduce process_stream_no_wrap and rewrite_no_wrap to skip wrapping

Enhancements:

  • Update core processing function to toggle wrapping based on flag
  • Adjust CLI logic to invoke wrap or no-wrap variants accordingly

Documentation:

  • Document --wrap usage in README

Tests:

  • Add integration test for the --wrap option

Summary by CodeRabbit

  • New Features
    • Added a new command-line option --wrap to control paragraph and list item wrapping to 80 columns.
  • Documentation
    • Updated documentation to clarify the behaviour and usage of the new --wrap option.
  • Tests
    • Introduced an integration test to verify the functionality of the --wrap command-line option.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jun 15, 2025

Reviewer's Guide

Refactors the text processing pipeline to make wrapping opt-in via a new --wrap CLI flag, updating core functions, command-line logic, documentation, and tests accordingly.

Sequence Diagram: Conditional Text Processing with --wrap Flag

sequenceDiagram
    actor User
    participant CLI_Main as "CLI (main.rs)"
    participant Lib_PublicAPI as "lib.rs (Functions)"
    participant Lib_Inner as "lib.rs (process_stream_inner)"

    User->>CLI_Main: Executes mdtablefix (optional --wrap)
    CLI_Main->>CLI_Main: Parses arguments (sets wrap_flag)

    alt wrap_flag is true
        CLI_Main->>Lib_PublicAPI: Calls wrapping function (e.g., process_stream or rewrite)
        Lib_PublicAPI->>Lib_Inner: process_stream_inner(data, true)
        Lib_Inner-->>Lib_PublicAPI: Wrapped lines
        Lib_PublicAPI-->>CLI_Main: Result with wrapped lines
    else wrap_flag is false
        CLI_Main->>Lib_PublicAPI: Calls non-wrapping function (e.g., process_stream_no_wrap or rewrite_no_wrap)
        Lib_PublicAPI->>Lib_Inner: process_stream_inner(data, false)
        Lib_Inner-->>Lib_PublicAPI: Non-wrapped lines
        Lib_PublicAPI-->>CLI_Main: Result with non-wrapped lines
    end
    CLI_Main->>User: Outputs processed text
Loading

File-Level Changes

Change Details Files
Refactor process_stream into an internal function supporting optional wrapping and introduce no-wrap variants
  • Extract process_stream_inner with a wrap parameter
  • Define process_stream (default wrapping) and process_stream_no_wrap
  • Implement rewrite_no_wrap alongside existing rewrite
src/lib.rs
Integrate --wrap flag into CLI logic for wrapping behavior
  • Add wrap boolean argument in Cli
  • Branch on cli.wrap to choose between streaming functions
  • Branch on cli.wrap for rewrite vs rewrite_no_wrap in in-place mode
src/main.rs
Add integration test for the new wrap option
  • Introduce test_cli_wrap_option to validate wrapping when --wrap is used
tests/integration.rs
Document the --wrap CLI option in README
  • Include --wrap in usage synopsis
  • Describe wrap behavior under the command-line usage section
README.md
Standardize code examples in doc comments
  • Tag fenced code examples with ignore to bypass doctest parsing
  • Escape backticks in regex examples for clarity
src/lib.rs
src/html.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 Jun 15, 2025

Walkthrough

This update introduces a --wrap command-line option to control whether paragraphs and list items are wrapped to 80 columns. The codebase is refactored to support processing with or without wrapping, exposing new and existing functions for both behaviours. Documentation and tests are updated accordingly.

Changes

File(s) Change Summary
README.md Updated usage instructions and clarified that wrapping is conditional on the --wrap flag.
src/html.rs Updated doc examples to no_run, simplified import paths, made html_table_to_markdown hidden public.
src/lib.rs Added hidden public wrapper for html_table_to_markdown, exposed internal utilities, refactored process_stream with wrap/no-wrap variants, added rewrite_no_wrap.
src/main.rs Added --wrap CLI flag, introduced helper functions to select wrap/no-wrap processing, updated main logic accordingly.
tests/integration.rs Added integration test verifying CLI --wrap option wraps lines to 80 columns.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI
    participant Library

    User->>CLI: Run mdtablefix [--wrap] [file]
    CLI->>CLI: Parse CLI arguments
    alt --wrap is set
        CLI->>Library: process_stream / rewrite (with wrapping)
    else --wrap not set
        CLI->>Library: process_stream_no_wrap / rewrite_no_wrap (no wrapping)
    end
    Library-->>CLI: Processed output
    CLI-->>User: Output to stdout or file
Loading

Possibly related PRs

Poem

A rabbit hopped with code so neat,
Now wrapping lines is at your feet.
With --wrap you choose the flow,
Long lines short, or let them grow.
Docs and tests all in a row—
This bunny’s work is good to go!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c68a57e and 19208ee.

📒 Files selected for processing (4)
  • src/html.rs (2 hunks)
  • src/lib.rs (8 hunks)
  • src/main.rs (2 hunks)
  • tests/integration.rs (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (4)
  • tests/integration.rs
  • src/html.rs
  • src/main.rs
  • src/lib.rs
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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

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

coderabbitai Bot added a commit that referenced this pull request Jun 15, 2025
Docstrings generation was requested by @leynos.

* #38 (comment)

The following files were modified:

* `src/html.rs`
* `src/lib.rs`
* `src/main.rs`
* `tests/integration.rs`
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 15, 2025

Note

Generated docstrings for this pull request at #39

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

🧹 Nitpick comments (2)
src/main.rs (1)

47-52: Minor duplication – extract helper to reduce branching

The if cli.wrap { … } else { … } block appears three times. Extracting a small helper (e.g. fn process(lines: &[String], wrap: bool) -> Vec<String>) would remove repetition and make future adjustments (different widths, etc.) less error-prone.

Pure refactor; no functional bug.

Also applies to: 58-63, 66-71

src/html.rs (1)

215-225: Public exposure of internal helper twice

html_table_to_markdown is now pub #[doc(hidden)] and re-exported at the crate root with the same visibility. This leaks the symbol via two paths (mdtablefix::html::html_table_to_markdown and mdtablefix::html_table_to_markdown). If complete hiding is the goal, consider:

-#[doc(hidden)]
-pub fn html_table_to_markdown(…)
+pub(crate) fn html_table_to_markdown(…)

and keep only the crate-level re-export tagged with #[doc(hidden)].

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4b452a9 and c68a57e.

📒 Files selected for processing (5)
  • README.md (2 hunks)
  • src/html.rs (2 hunks)
  • src/lib.rs (8 hunks)
  • src/main.rs (3 hunks)
  • tests/integration.rs (1 hunks)
🔇 Additional comments (2)
README.md (1)

4-5: Documentation update looks good

The README now accurately reflects the opt-in behaviour via --wrap. No further issues spotted.

Also applies to: 24-29

src/lib.rs (1)

505-513: Wrapper functions read cleanly

process_stream / process_stream_no_wrap correctly delegate to the shared inner helper. Nice separation of concerns.

Comment thread tests/integration.rs
@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jun 15, 2025

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 15, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@leynos leynos merged commit 1ca036e into main Jun 15, 2025
1 check passed
@leynos leynos deleted the codex/make-text-wrapping-optional branch June 15, 2025 11:01
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