fix(errors): surface Supabase query errors instead of swallowing them#237
Merged
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.
PostgrestError is a plain object, not a subclass of Error (unlike AuthError, StorageError and FunctionsError), so
e instanceof Errorwas false for any failed query: every call site fell back to a generic literal and dropped the real message — a broken feed showed "Error al cargar" with no trace anywhere.Add errorMessage() / reportError(), which log the underlying error and return the user-facing text, and route the six database call sites through them: useFeed, usePostEngagementMetrics, useUserList and the profile screen. Postgres jargon stays out of the UI but is no longer lost.