docs: add Refactoring Needed section to KNOWN_ISSUES.md#422
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request adds a "Refactoring needed" section to Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #422 +/- ##
=======================================
Coverage 90.30% 90.30%
=======================================
Files 49 49
Lines 19163 19163
Branches 220 220
=======================================
Hits 17306 17306
Misses 1853 1853
Partials 4 4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Adds a Refactoring Needed section to
KNOWN_ISSUES.mddocumenting four compiler/test files that have grown too large. Files and GitHub issues were identified by a full codebase audit.vera/wasm/calls.pytests/test_codegen.pytests/test_checker.pyvera/codegen/api.pyAlso labels the three historical refactoring issues (#99, #100, #155) with the new
refactorlabel.No code changes — documentation only.
Closes
No issues closed — this PR files and tracks new issues rather than resolving them.
🤖 Generated with Claude Code
Summary by CodeRabbit