Add integration test for debounced search clearing results when input is emptied

[Chucks1093]

Summary

When the user clears the search input completely, the creator list should revert to showing all creators without any search filter applied. An integration test should confirm this reset behavior fires correctly after the debounce delay.

Scope

• Type a search term and wait for the debounce to fire
• Clear the input and wait for the debounce delay again
• Assert the API was called with no search param on the second request
• Assert the full creator list is displayed

Acceptance Criteria

• Clearing input triggers a new API call with no search param
• Full unfiltered creator list displayed after clearing
• No search param present in the request after clear

ETA: 12 hours

---

Coordinate on Telegram

[NickiM84]

@NickiM84 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, I'm a fullStack developer with years of experience, I have worked on several projects, can I please work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @NickiM84 to this issue.

[oscar24357]

@oscar24357 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer I'd love to work on this issue, please assign me to it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @oscar24357 to this issue.

[charliechinedu19-netizen]

@charliechinedu19-netizen has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, please let me work on this.
I'll finish it up asap

ℹ️ Repo Maintainers: To accept this application, review their application or assign @charliechinedu19-netizen to this issue.

[VeronicDev]

@VeronicDev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer please assign me this , I'd really love to work on this. Thanks.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @VeronicDev to this issue.

[kingbitnation]

@kingbitnation has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi! I'd like to work on this issue.

After reviewing the requirements, I believe it's a good match for my experience. I'll implement the requested functionality while following the project's existing architecture, coding conventions, and contribution guidelines. I'll ensure the solution is clean, well-tested, and covers all of the stated acceptance criteria, updating or adding tests where appropriate and documenting any relevant changes.

If I encounter any implementation details that need clarification, I'll communicate them early to avoid unnecessary rework.

Could this issue be assigned to me?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kingbitnation to this issue.

[edehvalentine236-jpg]

@edehvalentine236-jpg has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer, I'm Valentine. I would love to resolve this issur. Kindly assign.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @edehvalentine236-jpg to this issue.

[drips-wave]

Congratulations, @kingbitnation! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @kingbitnation: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊