WIP: Add sync implementation from core extension #192
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 integrates the new sync logic implemented in the core extension (at powersync-ja/powersync-sqlite-core#70) into the Kotlin SDK.
Internally, the existing implementation has been renamed to "legacy implementation" (and I've annotated methods related to it with
@LegacySyncImplementation
which should make it easier to identify which methods we can eventually remove after we finish the migration).For now however, the new implementation is marked as experimental, and not enabled by default. Users will have to use Kotlin's opt-in mechanism for
ExperimentalPowerSyncAPI
to use it. So, the only API changes are:SyncOptions
class. Constructing a non-default instance of this class requires opting in toExperimentalPowerSyncAPI
.newClientImplementation
field can be set totrue
to use the new Rust client.method
can be set toConnectionMethod.Http
or toConnectionMethod.WebSocket
.In the sync stream, I've moved the existing methods into an inner
LegacyIteration
class, the newActiveIteration
class implements the sync logic by forwarding it to the PowerSync control interface in the core extension.