Skip to content

fix(web): show "No results." in virtualized empty tables - #93

Merged
debpalash merged 1 commit into
mainfrom
fix/datatable-virtual-empty-state
Oct 13, 2026
Merged

debpalash merged 1 commit into
mainfrom
fix/datatable-virtual-empty-state

Conversation

@debpalash

Copy link
Copy Markdown
Owner

Found while browser-verifying the react-table v9 migration (#81/#88); this predates it.

DataTable picked the virtualized body whenever enableVirtualization && virtualRows, and virtualRows is [] (truthy) when there are no rows, so the "No results." row never rendered. On /leads (virtualized by default), filtering companies to something with no match showed a blank table under "0 rows".

  • data-table.tsx: require rows.length for the virtualized branch so empty tables fall through to the empty state.
  • test_lead_selection_browser.py / fixture: also mount a default (virtualized) DataTable with no data and assert "No results." renders. Fails without the fix, passes with it.

🤖 Generated with Claude Code

The virtualized branch was chosen whenever virtualization was on, because
an empty virtual-item array is truthy, so the empty-state row never
rendered. On the Leads page a company filter matching nothing showed a
blank table.

Signed-off-by: debpalash <debash67@outlook.in>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@debpalash
debpalash merged commit 9188fc4 into main Oct 13, 2026
4 checks passed
@debpalash
debpalash deleted the fix/datatable-virtual-empty-state branch October 13, 2026 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant