Reviews: add "Most helpful" sort with helpful votes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- database, full-stack
Research direction
The issue proposes a review_votes table, a helpful toggle on /r/[slug], and a Most helpful sort. First read PRD §8.11 and issue #107 to understand the existing review sorts; then inspect the review page and its data access paths. The scope is still up for discussion, so confirm the voting rules with the maintainer before implementation; done means students can vote within those rules and reviews sort by vote count, then recency.
Written by the indexing model from the issue text.
Description
Problem
PRD §8.11's UX notes ask for reviews to be sortable by most recent, highest rated, and most helpful. #107 shipped the first two. "Most helpful" needs students to be able to mark reviews as helpful, which doesn't exist yet.
Proposed scope (for discussion before a PR)
- New
review_votestable:review_id(FK toreviews, deleted with the review),user_id,created_at, unique(review_id, user_id), RLS on. One new migration. - A "Helpful (N)" toggle on each review on
/r/[slug], for signed-in students. Students can't vote on their own review; this is checked on the server, and review authors stay anonymous. - Signed-out visitors see the count, and the button prompts them to sign in.
- A third sort link, "Most helpful": helpful count first, then most recent.
Questions for the maintainer
- Is this worth adding now, given how few reviews there are so far?
- Should a student have to have saved the resource (like writing a review does) before they can vote?
- Should votes be "helpful" only, or helpful/not helpful?
Out of scope: moderation or reporting of reviews.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 6
- Avg merge
- 21h 33m
- Merged PRs (30d)
- 48
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Your-Voldemort/StudentStack
-
CI passes NEXT_PUBLIC_SUPABASE_ANON_KEY but the app reads NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY; e2e job installs only ChromiumPossibly taken @rootsiemen claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Your-Voldemort/StudentStack#126 · 1 comment ·
Maintainers usually reply within 1 day
-
Flag curated flagship opportunities whose dates need a refreshPossibly taken @rootsiemen claimed this today. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
Your-Voldemort/StudentStack#120 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Your-Voldemort/StudentStack
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cloudscape-design/components#5184 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
JarX-Concepts/react-native-platform-components#130 ·
Maintainers usually reply within 1 day
-
fix(api): optimize-for-web /preview outer catches miss asDecoderOutOfMemory on V8 OOM and SIGKILLOpenarea: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
snapotter-hq/SnapOtter#3773 ·
Maintainers usually reply within 1 day
-
ai-driven-qa ux-audit
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/twake-contacts-frontend#386 ·
Maintainers usually reply within 1 day
-
git: README should state plainly that without --repository every reachable repository is in scopeOpendocumentation server-git v2
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
modelcontextprotocol/servers#5225 ·
Maintainers usually reply within 1 day