rm: the snapshot sync, once the log has shipped two releases (phase 4)

Open
#1,844 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
dart, flutter, sql
Domain
databases

Research direction

The removal touches SyncIface, BackupV2.merge, lastUpdateTs, the tombstone table and the m033 migration, so start by locating those symbols with a project-wide search. This is blocked by #1842 (theme packages must become records first), so it cannot start yet. Done means the sync step is gone while backup export and restore still work, which is a design-level change.

Written by the indexing model from the issue text.

Description

enhancement

Once the operation log has been in two releases: remove SyncIface/BackupV2.merge as a sync step, lastUpdateTs, the tombstone table and updated_at/rev as merge inputs, and the legacy-stamp seeding in m033. The backup stays as export/restore.

Blocked by #1842: theme packages must become records first, since they only travel in the backup today.

Dominant language
Dart
Stars
8.9k
Forks
573
Avg merge
6h 50m
Merged PRs (30d)
134

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lollipopkit/flutter_server_box

All issues in lollipopkit/flutter_server_box

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.