Repository navigation
feat: paginate job feeds by organization - #202
Merged
Merged
Conversation
|
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
2 participants
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.
Organization-heavy imports can fill an entire page with jobs from one employer. Add
/jobs/feedto paginate organizations by their newest matching job, with up to five jobs per stack, while keeping skill, organization, project, city, expert, and text searches as individual cards.The feed shares existing eligibility and filters, applies filters before grouping, uses deterministic database pagination, and preserves project employers. Pillar criteria use the same selection, exact organization IDs distinguish namesakes, and a metadata-only pillar response avoids loading the old 100-job list. Existing list endpoints remain compatible.
Validation: 1,114 unit tests, all 181 PostgreSQL integration tests (including 206 jobs, filter-before-limit, namesakes, older organization jobs beyond 100, and fully-remote parity), lint, and production build pass. Read-only production query measured 97 ms for 16,920 jobs / 1,145 entries; 47 selected card payloads passed web validation. No schema migration.