Sonarly Claude Code
524e68bd3a
https://sonarly.com/issue/17183?type=bug The virtualized record table's scroll-triggered data fetching has insufficient prefetching — the initial load covers only 60 records (6 pages), but the overscan window and debounce logic delay subsequent page fetches, causing visible skeleton placeholders during slow scrolling. Fix: Two changes in `RecordTableVirtualizedRowTreadmillEffect.tsx`: **1. Fixed the scroll speed dead zone (50-200 rows/s) where no data fetch was triggered** Previously, `triggerFetchPages()` was only called inside the `else if (speed < 50 rows/s)` branch. For scroll speeds between 50-200 rows/s (typical slow-to-medium scrolling), neither the high-speed nor low-speed branch would execute, meaning no data fetch was triggered during active scrolling. The only fallback was `handleAfterLastScrollDebounced` which required the user to stop scrolling for 300ms. The fix moves `triggerFetchPages()` outside the speed threshold branches so it fires on every scroll event regardless of speed. This is safe because: - `triggerFetchPages` itself is debounced (25ms with 2000ms maxWait) - `triggerFetchPagesWithoutDebounce` has an early return when `lowDetailsActivated` is true - Already-loaded pages are filtered out before any network request The speed thresholds now only control the low-details rendering mode (showing skeletons vs full cells during fast scrolling), which was their original intent. **2. Reduced `LAST_SCROLL_DEBOUNCE_TIME` from 300ms to 100ms** This is the debounce delay for `handleAfterLastScroll`, which fires after the user stops scrolling. 300ms felt sluggish — the user would see placeholders for a noticeable period after stopping. 100ms is fast enough to feel responsive while still batching rapid scroll-stop events.
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See: 🚀 Self-hosting 🖥️ Local Setup
Why Twenty
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Personalize layouts with filters, sort, group by, kanban and table views
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!