Skip to content

Implement No-Results State for Creator Search - #687

Open
Damilorlar wants to merge 1 commit into
accesslayerorg:mainfrom
Damilorlar:feature/search-no-results-state
Open

Implement No-Results State for Creator Search#687
Damilorlar wants to merge 1 commit into
accesslayerorg:mainfrom
Damilorlar:feature/search-no-results-state

Conversation

@Damilorlar

Copy link
Copy Markdown
Contributor

#Closed #675

Goal
Provide a dedicated no-results state when a creator search returns no matches, ensuring users receive clear feedback instead of the generic empty state intended for an unfiltered list.

Context
Currently, when a search query returns zero creators, the application displays the same empty state used when no creators exist at all. This makes it unclear whether the search yielded no matches or the list is simply empty. A distinct no-results state improves the user experience by explaining that no creators matched the search term.
Acceptance Criteria
Display a dedicated no-results message when a search returns zero creators.
The message references or acknowledges the user's search term.
The no-results state is visually and functionally distinct from the unfiltered empty state.
Clearing the search input removes the no-results state and restores the default view.
Add an integration test covering the no-results search behavior.
Implementation Notes
Mock the creator search API to return an empty array for the query zzznomatch.
Enter zzznomatch into the search input and wait for the mocked response.
Verify that the no-results message is displayed and includes the search term.
Confirm that the displayed state differs from the generic empty state shown for an unfiltered list.
Verify that clearing the search input removes the no-results state and returns the interface to its default state.

When a search query returns zero creators, the response now includes
the search term in data.meta.search so the frontend can display a
contextual no-results message instead of the generic empty state.

- Add CreatorListMeta type extending OffsetPaginationMeta with search
- Update serializers to accept and forward the search term
- Update controller to pass validatedQuery.search
- Add integration tests for the no-results search state
@Chucks1093

Copy link
Copy Markdown
Contributor

Fix Merge conflict

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.

2 participants