fix(structural): preserve decorator declaration provenance - #51
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI 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. WalkthroughPython structural analysis now includes decorators in class and function symbol spans and hashes. Tests verify that changing a function decorator marks the function as modified and includes the decorator in AST evidence. ChangesDecorator-aware declaration tracking
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to Decorator edits now correctly update declaration provenance and AST evidence. The change is covered by passing tests and compilation, with no merge-blocking risk identified. 🚥 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
Validation
python3 -m pytest -q(161 passed)git diff --checknpm run compile-testsinWildestAI/wildest-vscode-extCompatibility
No schema, CLI option, or JSON shape changed. This corrects existing symbol
change_kindand AST evidence for decorated Python declarations; the VS Code TypeScript consumer compiles against the unchanged v2 contract. Website release claims remain unchanged because this is unreleased.Part of #22
Remaining #22 work includes additional deterministic Python baseline and fixture coverage beyond decorated-declaration provenance.
Summary by CodeRabbit
Bug Fixes
Tests