bug: Body field can be exported now

[AbdulRehman-z]

Summary by CodeRabbit

• New Features
  • The TCP listener now includes the request body in its output. After headers, a “Body:” line is printed with the full payload.
  • The printed body reflects the complete request content once fully read.
  • No changes to commands, flags, or connection handling behavior.
  • Output formatting remains otherwise unchanged.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Expose the HTTP request body via a public Request.Body field, update tests accordingly, and add body printing in the TCP listener after headers. No control-flow or error-handling changes.

Changes

Cohort / File(s)	Summary
Expose Request.Body internal/request/request.go, internal/request/request_test.go	Rename Request struct field from body to Body; update assignment from buffer to Body; adjust tests to reference Body.
TCP listener output cmd/tcpListener/main.go	After printing headers, print a "Body: " line using r.Body.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Client
  participant Listener as TCP Listener
  participant Parser as Request Parser

  Client->>Listener: TCP request
  Listener->>Parser: Parse request
  Parser-->>Listener: Request{Headers, Body}
  Note over Listener: Previously printed headers only
  Listener->>Listener: Print headers
  Listener->>Listener: Print "Body: " + Request.Body

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A twitch of nose, a hop of glee,
The Body now made plain to see.
I nibble bytes and print with cheer,
Headers first, then truth appears.
Small refactor, tidy run—
Carrots logged, my work is done. 🐇📜

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between fcc788e and f51066f.

📒 Files selected for processing (3)

• cmd/tcpListener/main.go (1 hunks)
• internal/request/request.go (2 hunks)
• internal/request/request_test.go (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/optimization

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[AbdulRehman-z]

Good merging!