Add integration test for creator list price range filter combined with sort param

[Chucks1093]

Summary

The min_price / max_price filter params must work correctly when combined with a sort param. An integration test should confirm filtered results are also sorted correctly rather than just the full unfiltered list being sorted.

Scope

• Seed creators with varied prices
• Call the creator list with both a price range filter and sort=price_desc
• Assert only creators within the price range appear in the response
• Assert those creators are sorted highest price first

Acceptance Criteria

• Only creators within the price range are returned
• Results are sorted by price descending within the filtered set
• Creators outside the range are absent regardless of their sort position

ETA: 12 hours

---

Coordinate on Telegram

[kodinaka30-ship-it]

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

I'd like to work on this because filter and sort logic can silently break when combined. it's easy for a sort to apply to the full list before filtering, which would pass casual testing but fail this exact case. I'm comfortable seeding creators with varied prices, calling the endpoint with both min_price/max_price and sort=price_desc, and asserting the response only contains in-range creators sorted correctly. I'll specifically verify creators outside the range never appear, regardless of where they'd rank in an unfiltered sort.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kodinaka30-ship-it to this issue.

[Toyinoje]

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

Hello maintainer, I would love to work on this issue please assign me.

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

[T-kesh]

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

I'd like to work on this

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

[Ajibose]

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

kindly assign

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

[grantfox-oss]

🦊 GrantFox — @T-kesh has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #509)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @T-kesh: 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 🌊