Conversation
escape_content had no case for backslash, so it escaped the backslash of an escape sequence that was already in the source: `\]` became `\\]`, a literal backslash followed by a bare `]` that closes the caller's content block early. Copy escape sequences through whole instead.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe renderer now preserves existing backslash escape sequences during diff content escaping. Unit and integration tests verify that escaped brackets and asterisks are not double-escaped. ChangesEscape Preservation
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The renderer now preserves existing escapes without introducing a current merge-blocking risk. 🚥 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 |
escape_content had no case for backslash, so it escaped the backslash of an escape sequence that was already in the source:
\]became\\], a literal backslash followed by a bare]that closes the caller's content block early. Copy escape sequences through whole instead.Summary by CodeRabbit
\*and\[now display correctly.