fix(structural): preserve artifacts when parser dependencies are unavailable - #35
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus 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. WalkthroughThe parser now catches ChangesStructural parser error handling
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized change preserves valid artifacts when an optional parser is unavailable and reports the failure without changing the schema or CLI contract; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
PARSE_FAILUREinstead of aborting or fabricating structural changesValidation
python3 -m pytest tests/test_structural.py -qpython3 -m pytest -qgit diff --checkNo schema or CLI contract fields changed; the VS Code extension remains compatible.
Part of #22
Summary by CodeRabbit