RTK is parsing `rspec` default output as json, when it is not.

描述

⏺ Bash(cd ~/dev/chopin && bundle exec rspec redacted/path/to/my_spec.rb --no-color 2>&1 | grep -E "examples|Failure|passe…)
  ⎿  [rtk] rspec: JSON parse failed (expected value at line 1 column 1), using text fallback

⏺ RTK tries parse rspec output as JSON. Default rspec formatter = progress (text), not json. Fallback works but noisy.

  Options:
  - Ignore warning. Text fallback fine.
  - Run raw: rtk proxy bundle exec rspec ...
  - Force JSON: bin/rspec --format json ... (RTK parse success)
  - File RTK bug: formatter autodetect should skip JSON parse when --format not json.

貢獻者指南

技術棧

rust

領域

cli

議題類型

bug

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

2

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

under 1 hour

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

fresh

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

clear

前置要求

basic Rustunderstanding of JSON parsing

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

75

研究方向

The issue occurs when RTK tries to parse rspec output as JSON. The default rspec formatter is progress (text), not JSON. Look at the output parsing code in RTK (likely in a module handling shell command results). Find where JSON parsing is attempted and add a condition to skip it unless the user explicitly uses ` format json` in the rspec command. The existing text fallback already works, so the fix is to avoid the unnecessary JSON parse attempt.