Skip to content

Stabilize manuscript ordering by record modification time - #40

Merged
callumalpass merged 1 commit into
mainfrom
fix/writer-modified-order
Oct 28, 2026
Merged

callumalpass merged 1 commit into
mainfrom
fix/writer-modified-order

Conversation

@callumalpass

Copy link
Copy Markdown
Contributor

Problem

Writer already uses each SDK record’s mtime for the home list, newest first. Equal or unavailable timestamps fell back to translated title ordering, so title and locale changes could move records unnecessarily.

Changes

  • Preserve per-record modification-time ordering and break ties deterministically by path.
  • Keep records with missing or invalid times last; never substitute collection or sync time.
  • Add coverage for timestamp projection, local session saves, synced edits, unrelated sync events, and home-list refreshes.

Tests

  • rpnpm check passed (translation checks, typechecks, full unit suites).
  • Final targeted app run passed: 39 Vitest tests; 77 script tests passed, 2 existing skips.
  • git diff --check passed.

No release or deployment.

@callumalpass
callumalpass merged commit 491c96b into main Oct 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant