fix: preserve markdown fences in fancy reporter#434
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe fancy reporter's inline-code highlighting regex was changed to avoid matching markdown code fence backticks, preventing corruption of fenced code blocks during formatting. A new test verifies that fenced code blocks in log output are preserved correctly. ChangesFancy reporter backtick fix
Estimated code review effort: 1 (Trivial) | ~5 minutes Related issues: Suggested labels: bug, reporters Suggested reviewers: pi0 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Fixes #380.\n\n### What changed\n- Restrict inline backtick highlighting so it does not match across newlines or consume triple backticks from Markdown code fences.\n- Add a regression test that formats two adjacent fenced code blocks through the fancy reporter.\n\n### Validation\n- pnpm vitest run test/consola.test.ts\n- pnpm lint
Summary by CodeRabbit