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
1 participant
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.
Fixes PM-6496.
Make every data column in All Submissions sortable: handle, rating, submission date, and provisional/initial and final scores. Headers expose the active direction, mobile users can choose a field, and changing a field resets pagination. Action controls stay unsorted as requested.
Handle, rating, and score sorts fetch the complete latest-submission collection in bounded page batches, hydrate the displayed profile/score values, then sort before paginating. Missing and unreleased numeric values stay last in either direction. Date sorting continues to use server pagination, and My Submissions retains date ordering.
Validation: 180 challenge detail/service tests pass, including ascending/descending numeric sorts, hydrated profiles, missing values, cross-page sorting, pagination reset, complete collection fetching, and failed-page handling; full
yarn lint; productionyarn run buildwithNODE_OPTIONS=--max-old-space-size=8192.