Skip to content

Fix modification date not updating after note edit#5

Merged
asabirov merged 1 commit into
main-forkfrom
fix/modification-date-on-edit
Mar 28, 2026
Merged

Fix modification date not updating after note edit#5
asabirov merged 1 commit into
main-forkfrom
fix/modification-date-on-edit

Conversation

@asabirov
Copy link
Copy Markdown
Owner

Summary

  • Fixed modified record-level metadata passing through the old timestamp from the original record in updateNote() and trashNote(), causing CloudKit to not recognize the update and leaving sf_modificationDate unchanged
  • Bumps version to 0.3.3

Test plan

  • Run bcli edit <id> --stdin and verify bcli ls shows updated Modified date
  • Run bcli edit <id> --editor and verify Modified date updates
  • Run bcli trash <id> and verify modification date is current

The modified record-level metadata was passing through the old timestamp
from the original record, causing CloudKit to not recognize the update.
Now uses the current timestamp for the modified metadata in both
updateNote() and trashNote().

Also bumps version to 0.3.3.
@asabirov asabirov merged commit 6337dec into main-fork Mar 28, 2026
asabirov pushed a commit that referenced this pull request Apr 7, 2026
…ields and preserving vector clock on parse failure

Updates updateNote() to send version and uniqueIdentifier fields that Bear
desktop requires to properly process sync updates. Also fixes
incrementVectorClock() to preserve the existing clock unchanged when parsing
fails, instead of resetting to counter=1 which caused sync conflicts.

Fixes #5
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