mirror of
https://github.com/Darkrock-Studios/hammer-editor.git
synced 2026-08-13 11:33:15 +00:00
The previous comment claimed the range assertion proved the edit "round-tripped instead of being stamped with NOW() server-side." It doesn't — server-side NOW() during sync falls in the same window. Replace with an honest description: storeAllBuffers inside prepareForSync bumps lastEdited right before upload, and the debounced contentFlow can fire again post-sync, so client-bumped-during-sync and server-stamped- on-receipt are observationally identical without instrumenting the sync pipeline. The range check still rules out drops, epoch-0 resets, and clearly-wrong stamps. |
||
|---|---|---|
| .. | ||
| src/jvmTest/kotlin/com/darkrockstudios/apps/hammer/integration | ||
| build.gradle.kts | ||