fix(react-virtual): make directDomUpdates a no-op without containerRef#1201
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 (5)
📝 WalkthroughWalkthroughWhen ChangesdirectDomUpdates no-op without containerRef
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 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)
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 |
|
View your CI Pipeline Execution ↗ for commit 4dd2834
☁️ Nx Cloud last updated this comment at |
🎯 Changes
Make
directDomUpdatesa no-op for direct DOM writes whencontainerRefis omitted. Previously the virtualizer still wrote item positions while never sizing the container (a broken half-state). Now omittingcontainerRefskips all direct writes while still skipping re-renders, letting consumers own the DOM updates themselves (e.g. inonChange).✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit
Bug Fixes
Documentation
Tests