Repository navigation
fix(unplugin): keep aliased named imports in definePage extraction - #2832
Conversation
✅ Deploy Preview for vue-router canceled.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughNamed-import filtering now checks whether each local binding is used and preserves the original imported name and alias. A test covers a used aliased import. ChangesAliased named imports
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The change preserves aliased imports used in definePage, and the test covers the expected generated import. No concrete merge-blocking risk is evident. 🚥 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 |
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2832 +/- ##
==========================================
+ Coverage 88.26% 88.27% +0.01%
==========================================
Files 78 78
Lines 6305 6305
Branches 2048 2070 +22
==========================================
+ Hits 5565 5566 +1
+ Misses 651 650 -1
Partials 89 89 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Fix
definePageextraction, which currently drops aliased named imports that are used inside thedefinePage({...})options object.Summary by CodeRabbit