Add dedicated "Most popular" sort to the loop library#90
Merged
Conversation
Co-authored-by: mberman84 <mberman84@users.noreply.github.com>
Co-authored-by: mberman84 <mberman84@users.noreply.github.com>
…ort-c5db Co-authored-by: mberman84 <mberman84@users.noreply.github.com>
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.
Summary
Adds a standalone Most popular option to the homepage sort control. Votes previously only influenced ordering as a tiebreaker inside "Featured, then popular"; this makes community votes directly browsable.
Most popularoption in the sort select, ordering rows by upvotes (ties fall back to newest)comparePopularcomparator and live vote totals from/api/votes, so rows re-rank when votes load or change?sort=popularwork through the existing URL state handling20260702-popular-sorton all three shell pages so browsers fetch the updated script after the next publishVerification
node --check loop-library/site/script.jsnode loop-library/scripts/check.mjsnpm --prefix loop-library/worker run check(47/47 tests pass)git diff --checkcleanNo Worker or schema changes; this is shell-only and takes effect with the next site publish.