Skip to content

Title: Add No-Results State for Creator Search - #850

Open
Damilorlar wants to merge 15 commits into
accesslayerorg:mainfrom
Damilorlar:no-results-state
Open

Title: Add No-Results State for Creator Search#850
Damilorlar wants to merge 15 commits into
accesslayerorg:mainfrom
Damilorlar:no-results-state

Conversation

@Damilorlar

Copy link
Copy Markdown
Contributor

##closed #675

Update the creator search experience to display a dedicated no-results state when a search query returns zero creators. The message should acknowledge the search term instead of showing the generic empty state used when no search is applied.

Add an integration test that searches for zzznomatch, verifies the no-results message is displayed and distinct from the unfiltered empty state, and confirms that clearing the search input removes the no-results state.

Add a  field ( |  | ) and an optional
 to the creator list response envelope so clients can render a
tailored no-results message referencing the search term instead of the
generic empty state. Includes an integration test covering the
zzznomatch zero-result search scenario.
…config.schema, error.constants, creator.routes, test files
…, move STELLAR_AUTH_SECRET to proper property
…rCode, duplicate keyId declaration in creator routes
@Chucks1093

Copy link
Copy Markdown
Member

❌ CI Failed — verify (Server CI)

The verify check is failing on this PR. This is a long-open PR — the branch may be significantly out of date with main.

Likely causes:

  • Branch is out of date with main causing import conflicts or missing dependencies
  • TypeScript type mismatch from an interface that changed in main
  • Failing tests due to logic that has since changed

Steps to fix:

  1. Rebase on latest main: git fetch origin && git rebase origin/main
  2. Resolve any conflicts, then run npm run build
  3. Run npm test and fix any failing tests
  4. Push

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