mirror of
https://github.com/johannesjo/super-productivity.git
synced 2026-07-19 01:17:31 +00:00
32aec63023
* cleanup: remove unused latestSnapshotSeq from HTTP response and client types latestSnapshotSeq was computed on every download but never read by any client code. sibling snapshotVectorClock IS consumed — only this field is dead. The server still computes it internally for the snapshot optimization logic, but it no longer serializes it in the response. Removed from: - DownloadOpsResponse type and response object (sync.routes.ts) - Zod schema (supersync-http-contract.ts) + associated test - OpDownloadResponseBase interface (sync-providers) - Client validator test + stale comment references - Server integration test assertions * cleanup: remove deprecated CONFLICT_STALE error code Server never emits CONFLICT_STALE (fully migrated to CONFLICT_SUPERSEDED). * cleanup: remove unused SyncConfig fields (maxOpsPerUpload, downloadLimit, downloadRateLimit) These three config fields were declared and defaulted but never read by any code. Routes hardcode their own limits: - maxOpsPerUpload: gate is MAX_OPS_PER_BATCH constant (sync.routes.payload.ts) - downloadLimit: hardcoded Math.min(limit, 1000) in sync.routes.ts - downloadRateLimit: hardcoded max:200 in route rateLimit config * cleanup: remove dead/drifted duplicate types from sync.types.ts Removed 6 types with zero references repo-wide: - SnapshotResponse: orphaned after previous PR removed its importers - UploadSnapshotRequest: zero uses, missing 7 fields vs actual Zod schema - RestorePointType: zero uses, included dead 'DAILY_BOUNDARY' value - RestorePoint: zero uses (live version in snapshot.service.ts) - RestorePointsResponse: zero uses - RestoreSnapshotResponse: zero uses |
||
|---|---|---|
| .. | ||
| conflict-detection-sql.integration.spec.ts | ||
| multi-client-sync.integration.spec.ts | ||
| snapshot-skip-optimization.integration.spec.ts | ||
| snapshot-vector-clock-sql.integration.spec.ts | ||
| websocket-storm.integration.spec.ts | ||