fix: pretty-print raw params and handle escaped newlines

[vadimtrunov]

Summary

• Pretty-print JSON in raw params section with proper indentation and replace escaped \n with actual newlines for readability
• Fix Task result title function to handle serialized JSON arrays consistently (applies same parse-if-string logic as getContentProps)

Addresses feedback from #391 review by @blackmammoth (raw params showing literal \n characters) and CodeRabbit suggestion for title consistency.

🤖 Generated with Claude Code

Summary by CodeRabbit

Bug Fixes

• JSON content displayed in chat parameters is now automatically formatted with proper indentation and escaped newlines converted to readable line breaks, improving clarity
• Results from agent tasks with array-based content are now handled more robustly, with improved detection and consistent rendering of multi-part responses in markdown format

[coderabbitai]

Walkthrough

The changes improve JSON content handling in the chat tools UI. One file adds error-tolerant JSON parsing and pretty-printing for raw parameters, while another enhances subagent Task result logic to recognize JSON-serialized arrays delivered as strings and render them consistently.

Changes

Cohort / File(s)	Summary
JSON Parsing & Display Enhancements src/components/chat/tools/components/CollapsibleDisplay.tsx, src/components/chat/tools/configs/toolConfigs.ts	Added error-tolerant JSON parsing in CollapsibleDisplay to pretty-print valid JSON with escaped newlines converted to actual newlines. Enhanced toolConfigs to detect and parse JSON-serialized array content in Subagent Task results, with robust content rendering that concatenates text fields from arrays or stringifies content as needed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• fix: parse serialized JSON content in subagent Task results #391: Modifies the same Subagent Task result handling in toolConfigs.ts to parse JSON-serialized string content into arrays/strings for proper rendering.

Suggested reviewers

• blackmammoth

Poem

🐰 JSON strings transformed with care,
Arrays hiding everywhere,
Pretty-prints with spaces true,
Newlines escape and born anew! ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: pretty-print raw params and handle escaped newlines' accurately reflects the main changes across both modified files: JSON pretty-printing and escaped newline handling in CollapsibleDisplay.tsx, plus related serialization handling in toolConfigs.ts.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}

[coderabbitai]

🤖 Fix all issues with AI agents

Verify each finding against the current code and only fix it if needed.


In `@src/components/chat/tools/components/CollapsibleDisplay.tsx`:
- Around line 70-76: The current inline IIFE in CollapsibleDisplay that returns
JSON.stringify(JSON.parse(rawContent), null, 2).replace(/\\n/g, '\n') mutates
escaped newlines and produces invalid JSON; remove the .replace(/\\n/g, '\n') so
the code returns a valid, pretty-printed JSON string (use
JSON.stringify(JSON.parse(rawContent), null, 2) directly), or if you want
human-readable unescaped newlines only for presentation, perform the replacement
at the rendering layer (after generating the pretty JSON) rather than altering
the JSON string itself; reference: CollapsibleDisplay and the rawContent
handling using JSON.parse/JSON.stringify.

🧹 Nitpick comments (1)

🤖 Fix all nitpicks with AI agents

Verify each finding against the current code and only fix it if needed.


In `@src/components/chat/tools/components/CollapsibleDisplay.tsx`:
- Around line 70-76: The current inline IIFE in CollapsibleDisplay that returns
JSON.stringify(JSON.parse(rawContent), null, 2).replace(/\\n/g, '\n') mutates
escaped newlines and produces invalid JSON; remove the .replace(/\\n/g, '\n') so
the code returns a valid, pretty-printed JSON string (use
JSON.stringify(JSON.parse(rawContent), null, 2) directly), or if you want
human-readable unescaped newlines only for presentation, perform the replacement
at the rendering layer (after generating the pretty JSON) rather than altering
the JSON string itself; reference: CollapsibleDisplay and the rawContent
handling using JSON.parse/JSON.stringify.

src/components/chat/tools/components/CollapsibleDisplay.tsx (1)

70-76: The \\n replacement may unintentionally alter JSON structure.

After JSON.stringify, literal \n sequences inside string values are the correct JSON encoding of newlines. Replacing them here means the output is no longer valid JSON — it's a hybrid of JSON structure with unescaped newlines inside string values. If the goal is readability this is fine, but worth noting that \t and other escape sequences (e.g., \") are left intact, creating an inconsistency.

If the intent is purely to make embedded newlines visible, consider doing the replace only on the display string rather than all \n sequences, or document that this is intentional pretty-printing for human consumption, not valid JSON.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/chat/tools/components/CollapsibleDisplay.tsx` around lines 70
- 76, The current inline IIFE in CollapsibleDisplay that returns
JSON.stringify(JSON.parse(rawContent), null, 2).replace(/\\n/g, '\n') mutates
escaped newlines and produces invalid JSON; remove the .replace(/\\n/g, '\n') so
the code returns a valid, pretty-printed JSON string (use
JSON.stringify(JSON.parse(rawContent), null, 2) directly), or if you want
human-readable unescaped newlines only for presentation, perform the replacement
at the rendering layer (after generating the pretty JSON) rather than altering
the JSON string itself; reference: CollapsibleDisplay and the rawContent
handling using JSON.parse/JSON.stringify.

[blackmammoth]

Hello @vadimtrunov, can you resolve the merge conflicts?