feat(backend): add combined search and discovery endpoint#320
Merged
Conversation
|
@Ezeh20 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Kaylahray
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Template
Description
Adds a dedicated discovery API that returns combined search results across posts, users, and trending topics in one normalized payload.
Fixes #307
Fixes the discovery API issue for unified search across posts and people.
This change introduces
/api/discoveryso the frontend can make one request for mixed discovery results instead of stitching together separate post and leaderboard/user calls. It supports query filtering, pagination, and ranking options, and returns a normalized result shape the search UI can render directly without extra reshaping.It also adds documentation for the endpoint in
app/docs/discovery-api.md.Checklist
npx prisma generateafter schema changesnpx prisma migrate devornpx prisma migrate deployas appropriateNotes:
corepack pnpm exec vitest run tests/api/discovery.test.tsnpx prisma generateapp/docs/discovery-api.mdPost-Merge Steps for Maintainers
If this PR includes changes to the Prisma schema:
Run the following command to apply the migration to your database: