Feature: Improvements for the data sync feature

[williscool]

Contrary to what the power sync library will try to make you believe the sync is not instant to your supabase pg setup.

There's a whole bunch of operations that happen in the background to make all of the events get properly synced up.

And I wouldn't consider the sinking actually being done until that is done.

So what I ended up to it is building a debug thing in the settings UI where I could watch the operation counts go up until it stops and that's how I know the sync is actually complete.

Also the insert into that we do there's weirdness when things get updated. I never had time to dig into.

So I end up just clearing out the previous events.

Which is not how it was originally intended to work you were supposed to just be able to tap the sync button and it would just figure out it out (by which I mean only sync events that are still in the active state and not dismissed)

So we should either

a) fix that
b) Make the sync button be a delete and re-update because that's what I end up actually doing

[williscool]

refs: #86 (comment)

and #93

[williscool]

opus 4.6 in cursor plan first draft (excellent example of detail I want for small to medium sized plans)

Now I have a complete picture. Here's my proposed plan:

---

Plan: Data Sync Improvements (Issue #260)

Context

• Current workflow: You manually open Danger Zone, clear remote events, then tap sync, then watch the debug JSON to know when it's done
• Goal: Formalize that into one button + show clear progress so you know the data your rescheduling app consumes is correct and complete

Phase 1: Formalize "Delete + Re-upload" as the primary sync action

Files to modify:

• src/lib/orm/index.ts — Add a psResyncTable() function that combines psClearTable + psInsertDbTable in sequence
• src/lib/features/SetupSync.tsx — Replace the current handleSync to call the new combined resync function; update button label (e.g., "Full Resync to Remote")

The old individual "Clear Remote PowerSync Events" button stays in the Danger Zone for manual use. The current "Sync Events Local To PowerSync Now" button becomes the full delete-and-reupload action.

Phase 2: Sync progress indicator

Key insight: PowerSync exposes SELECT COUNT(*) FROM ps_crud which gives the number of pending upload operations in the queue. Combined with currentStatus.dataFlowStatus.uploading, we can build a real progress indicator.

Flow:

1. User taps "Full Resync" — button goes disabled/loading
2. Clear runs → inserts run → ps_crud count spikes (all the deletes + inserts queued)
3. PowerSync SDK starts uploading → dataFlowStatus.uploading = true
4. UI polls ps_crud count and shows: "Uploading: X operations remaining"
5. When ps_crud count hits 0 and uploading is false → "Sync complete!" with timestamp
6. Button re-enables

Files to modify:

• src/lib/features/SetupSync.tsx — Add progress state, poll ps_crud count during sync, render a status banner (count + uploading state)
• Possibly extract a small useSyncProgress hook if the logic gets complex

What stays the same

• Connector.ts uploadData — no changes needed, it already handles the CRUD queue correctly with retries
• Danger Zone — keeps its individual clear button
• Sync Debug screen — still shows raw status/logs for deep debugging

What this does NOT address yet (future / Phase 3)

• Investigating the "update weirdness" with dismissed events lingering — the delete+reupload approach sidesteps this for now, which is exactly what you want
• Bidirectional sync — stays as-is

---

Does this plan look right to you? Any adjustments before I start implementing?