Search No Matches
Zero-result state echoing 3 active filter chips, the count 0 of 124, and per-filter recovery suggestions with item counts.
Zero-result state echoing 3 active filter chips, the count 0 of 124, and per-filter recovery suggestions with item counts.
The Application Collection unlocks the source for every Application block. All Access unlocks every Collection.
Already purchased? Log in
Search No Matches is the zero-result state for an in-app filtered list. The active filter set is echoed as removable chips: Status: Done, Assignee: Priya Nair, and Priority: Critical. Below them the honest count reads 0 of 124 items match all 3 filters, followed by the specific explanation No tasks assigned to Priya Nair with Critical priority are marked Done. The bottom panel is titled Suggested: remove one filter and offers two rows, one to remove Status: Done opening up to 38 items, and one to remove Priority: Critical opening up to 11, each with a Remove button. A Clear all 3 filters ghost button anchors the footer.
Filters are a typed array with a loosens flag. The item count in the suggestion rows is what separates useful guidance from a generic try fewer filters message.
Reach for this block wherever a filtered list can return zero rows, wired to your filter state and a count query that returns per-filter match counts. Keep the suggestion rows dynamic so each one shows the real recovery count.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the filtered task list zero state. Other no-match patterns:
Tip: name the filter to drop and show how many items it recovers; generic loosen your filters helps nobody.