You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Divergence] Tauri plugin reports priority sync status, so hasSynced, lastSyncedAt and waitForFirstSync work (powersync-js #1147) #698
What's changing: The Tauri plugin now forwards the Rust SDK's per-priority sync status to JavaScript. SyncStatus.hasSynced, lastSyncedAt and priorityStatusEntries are populated, and db.waitForFirstSync() resolves. Before this change the plugin always reported an empty priority status. The change is unreleased: it is in a pending changeset for tauri-plugin-powersync and depends on the Rust SDK 0.1.1.
High priority — existing docs are now inaccurate or incomplete
Tauri SDK Reference (https://docs.powersync.com/client-sdks/reference/tauri), "Limitations" section: states that the Rust SDK does not provide lastSyncedAt, hasSynced and priorityStatusEntries on SyncStatus, and tells readers to use SyncStatus.forStream instead. These properties are now available, so the limitation no longer applies. The alpha Warning at the top of the page also links to this limitations section.
For reviewer consideration — worth documenting
None beyond the page above. Related: #692 covers the Rust SDK API this change builds on (powersync-native #48), and open docs PR #694 ("Add more Rust snippets, remove outdated Tauri limitation") already touches this page.
Filed automatically by Claude Code (claude-sonnet-5-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.
This issue duplicates #692. That issue already has a comment covering powersync-js#1147 and the Tauri SDK Reference "Limitations" section, which I missed because I checked issue bodies and not their comments. Consider closing this one in favor of #692.
Activity
benitav commentedon Oct 15, 2026
This issue duplicates #692. That issue already has a comment covering powersync-js#1147 and the Tauri SDK Reference "Limitations" section, which I missed because I checked issue bodies and not their comments. Consider closing this one in favor of #692.
Generated by Claude Code