bug(#631): match fails on empty substs#633
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 (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughrunMatch now throws an EmptySubstsOnMatch CmdException when pattern matching produces no substitutions instead of only logging a debug message. A new exception constructor and Show message were added, and a test was added to assert the failing behavior. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@test/CLISpec.hs`:
- Around line 1030-1035: Remove the trailing whitespace at the end of the
withStdin argument in the test case labeled "fails on empty substitutions" so
the line containing withStdin "{Q.x.y}" has no extra spaces after the closing
brace; this fixes the fourmolu/formatter failure referenced in the test using
testCLIFailed and withStdin.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d9f48d94-89a7-47a4-a2fb-bd84d1429058
📒 Files selected for processing (3)
src/CLI/Runners.hssrc/CLI/Types.hstest/CLISpec.hs
|
@rultor merge |
@maxonfjvipon OK, I'll try to merge now. You can check the progress of the merge here. |
@maxonfjvipon Done! FYI, the full log is here (took me 19min). |
|
@maxonfjvipon Hey! Nice work on that contribution – you've bagged +12 points this time! 🎯 Here's the breakdown: +16 base points, but -4 for keeping it lean with just 10 hits-of-code (our policy encourages at least 40 for the full bonus). Still, quality over quantity – keep them coming! Your running score sits pretty at +122, and don't forget to peek at your Zerocracy account for the latest updates. |
Closes: #631
Summary by CodeRabbit
Bug Fixes
Tests