Supabase error handling #274
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
# Conflicts: # core/src/commonMain/kotlin/com/powersync/db/driver/SingleConnectionPool.kt # integrations/sqldelight/build.gradle.kts
simolus3
force-pushed
the
supabase-error-handling
branch
from
0f5d4ed to
99d5f1a
Compare
stevensJourney
previously approved these changes
Oct 1, 2025
...rations/supabase/src/commonMain/kotlin/com/powersync/connector/supabase/SupabaseConnector.kt
Outdated
Show resolved
Hide resolved
stevensJourney
previously approved these changes
Oct 1, 2025
stevensJourney
approved these changes
Oct 2, 2025
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.
This expands the supabase connector to make it
openand allow a few methods to be customized:openmethod.openmethod.This is to address this reported issue where a user wants to report errors to Crashlytics. At the moment, because the connector is final and catches fatal Postgres exceptions by (apart from a logger, essentially silently) deleting local writes, that would be tricky to detect (it doesn't even show up as an upload error in the sync status).
To clean up some top-level directories, this also moves the Supabase connector into the
integrations/folder. The maven artifact id is not affected by this because of agradle.propertiesfile with aPOM_ARTIFACT_IDentry.