Repository navigation
Add filters and challenge counts to the challenge listing and managed projects endpoints - #1303
Merged
Merged
Conversation
…nd page it by name
|
CollinBeczak
marked this pull request as ready for review
October 30, 2026 20:05
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.



Adds what the v4 Manage Challenges and Manage Projects pages need to page and filter on the server. All changes are additive, so existing clients are unaffected.
GET /challenges/listingsearchString,onlyOwned,onlyArchived,challengeIds.parentName.pagestill works as before (it's used as a row offset).GET /projects/managedisArchived,projectIds.challengeCounts: { total, completed }, so the frontend no longer has to download every challenge to show counts.Frontend PR: maproulette3
manage-challenges-pagination(merge this one first).