Open
Conversation
stevensJourney
approved these changes
Feb 18, 2026
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.
In tests for our Swift SDK, we use
:memory:as a file path with the intention of creating in-memory databases. This isn't actually the case though,:memory:is appended to the default database directory to create a database file of that name.This adds a method to
:PowerSyncKotlinthat will let the Swift SDK open in-memory databases. The Swift SDK can't callPowerSyncDatabase.openInMemorybecause that requires aCoroutineScopewe can't construct in Swift. So I've hidden those methods and added another factory next toopenPowerSyncWithPoolto create an in-memory connection.