Accept TAB command separators

[mjc]

Summary

• recognize TAB as a legal command separator in borrowed request parsing
• keep existing space-separated command behavior unchanged

Branch-added tests

• A parser regression test feeds a command line separated by TAB and verifies the command and arguments are split exactly as for a space.
• The request parser suite continues to cover malformed, empty, and multi-argument lines.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 8d807d17-535b-4818-8214-b4886348ea06

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

🟢 Approval recommended

The change is minimal, well-scoped, and includes a targeted regression test for the new TAB-separator behavior.

Pull request overview

This PR updates NNTP request parsing so that a TAB (\t) is accepted as a valid command separator (in addition to the existing space separator), while preserving existing behavior for space-separated commands.

Changes:

• Update RequestLine::parse to split on either space or TAB.
• Add a regression test ensuring a TAB-separated ARTICLE command is parsed identically to the space-separated form for kind/args/message-id routing.

File summaries

File	Description
src/protocol/request.rs	Accept TAB as a request verb/args separator and add a unit test covering the new behavior.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.