-
Notifications
You must be signed in to change notification settings - Fork 46
fix: use .maybeSingle() in reviews route to prevent 500 on not-found #445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
tankgxy
wants to merge
1
commit into
profullstack:master
from
tankgxy:fix/reviews-route-maybe-single
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewafter insert causes crashSwitching the INSERT+SELECT from
.single()to.maybeSingle()means bothdataanderrorcan benullwhen Supabase allows the INSERT but the follow-up SELECT is blocked (e.g., a row-level-security policy that permits writes but not reads). Theif (createError)guard on line 246 passes cleanly, and the code then crashes withTypeError: Cannot read properties of null (reading 'id')at every subsequent reference:review.id(lines 259, 265, 270, 275, 280, 284, 294, 297),review.reviewer, andreview.reviewee. A missing-row null check needs to be added after the error guard, or.single()should be retained for this INSERT case since a successful insert always returns exactly one row.