public/librenotes
1
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

Implement background sync on reconnect with conflict detection #23

New Issue
Open
opened 2026-02-25 16:05:16 +01:00 by libretech · 0 comments
libretech commented 2026-02-25 16:05:16 +01:00
Owner
Copy Link

Summary

Automatically sync offline changes when connectivity is restored, with conflict detection and resolution.

Implementation Tasks

  • Detect connectivity changes (online/offline events)
  • Push dirty notes to server on reconnect
  • Pull remote changes and merge with local state
  • Detect conflicts (local and remote both modified since last sync)
  • Present conflict resolution UI to user
  • Update sync timestamps after successful sync

Conflict Detection Strategy

  • Compare synced_at timestamps with server updated_at
  • If both changed since last sync, flag as conflict
  • Resolution options: keep local, keep remote, or manual merge

Acceptance Criteria

  • Offline edits sync automatically when reconnected
  • Concurrent edits on same note trigger conflict detection
  • User can resolve conflicts via UI
  • Sync state is visible (pending, syncing, synced, conflict)
## Summary Automatically sync offline changes when connectivity is restored, with conflict detection and resolution. ## Implementation Tasks - [ ] Detect connectivity changes (online/offline events) - [ ] Push dirty notes to server on reconnect - [ ] Pull remote changes and merge with local state - [ ] Detect conflicts (local and remote both modified since last sync) - [ ] Present conflict resolution UI to user - [ ] Update sync timestamps after successful sync ## Conflict Detection Strategy - Compare synced_at timestamps with server updated_at - If both changed since last sync, flag as conflict - Resolution options: keep local, keep remote, or manual merge ## Acceptance Criteria - [ ] Offline edits sync automatically when reconnected - [ ] Concurrent edits on same note trigger conflict detection - [ ] User can resolve conflicts via UI - [ ] Sync state is visible (pending, syncing, synced, conflict)
libretech added the
phase-4
 label 2026-02-25 16:05:16 +01:00
libretech changed title from Background sync to Implement background sync on reconnect with conflict detection 2026-02-28 09:35:29 +01:00
libretech added the
task
 label 2026-02-28 09:35:29 +01:00
libretech added the
frontend
 label 2026-03-01 20:32:36 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
backend
Backend changes
database
Database changes
documentation
Documentation improvements
epic
frontend
Frontend changes
infrastructure
Infrastructure and deployment
launch
Launch and release tasks
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
security
Security-related
task
Actionable task
No Label
frontend
phase-4
task
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
libretech
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: public/librenotes#23
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?