mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-18 16:12:11 +00:00
fix(backup): carry the symptoms an account made, and stop dropping the ones it cannot find
restoreCycleData was loud about one missing reference and silent about another, three lines apart. An unknown cycle reference threw; an unknown symptom key was filtered out of the list, so the day-log came back with one of its symptoms quietly gone and the restore reported success. The cause was upstream: the seeded catalogue is reference data every instance has, but a symptom the user created lives only in their account and was never carried. The key had nothing to resolve against, and the filter turned that into silence. Both ends now. The account's own definitions travel with the backup, the seeded rows deliberately do not — shipping those would let one instance's restore rewrite another's reference data. And the resolve step throws on an unresolvable key rather than filtering it, so the same function answers the same question the same way twice. Widening the builder's client type made four export tests fail on a missing delegate, which is the sweep working: those are the call sites, named by the compiler instead of found by reading.
This commit is contained in:
1 parent
a2e9587781
commit
b2e19ce0b6
5 files changed
+189
-6
No files matched your search
@@ -18,6 +18,7 @@ vi.mock("@/lib/db", () => ({
|
||||
cycleProfile: { findUnique: vi.fn().mockResolvedValue(null) },
|
||||
menstrualCycle: { findMany: vi.fn().mockResolvedValue([]) },
|
||||
cycleDayLog: { findMany: vi.fn().mockResolvedValue([]) },
|
||||
cycleSymptom: { findMany: vi.fn().mockResolvedValue([]) },
|
||||
// v1.28 backup-completeness — the records section the shared payload
|
||||
// builder now also reads (`buildRecordsBackupSection`).
|
||||
labResult: { findMany: vi.fn().mockResolvedValue([]) },
|
||||
|
||||
Reference in new issue
Block a user