fix: document safer conflict preservation

This commit is contained in:
vorotamoroz committed 2026-07-07 12:05:40 +00:00
1 parent eed0fca8d3
commit dbcbf2c5ca
2 files changed
+2 -2

No files matched your search

+1 -1
Submodule src/lib updated: 5ea74b5d87...a0efb7274e.
+1 -1
View File
@@ -13,7 +13,7 @@ The head note of 0.25 is now in [updates_old.md](https://github.com/vrtmrz/obsid
- When one side deletes a line and the other side modifies that same line, the conflict is preserved instead of silently choosing one side. - When one side deletes a line and the other side modifies that same line, the conflict is preserved instead of silently choosing one side.
- Fixed an issue where applying a newer database entry to storage could incorrectly preserve an older local file as a conflict (#994). - Fixed an issue where applying a newer database entry to storage could incorrectly preserve an older local file as a conflict (#994).
- Behaviour change: - Behaviour change:
- Local storage is preserved as a conflict when it may contain unsynchronised changes that are not represented in the revision history. If the incoming database entry is clearly newer, it is applied to storage instead. - Local storage is preserved as a conflict when it may contain unsynchronised changes that are not represented in the revision history. A newer incoming text entry is applied without creating a conflict only when it clearly extends the existing local text.
## 0.25.79 ## 0.25.79