Skip to content

Event Notes 0.3.8

Latest

Choose a tag to compare

@github-actions github-actions released this 16 Nov 14:27
21fddf8

Event Notes 0.3.8

Event Notes that lose their calendar event, because a calendar was removed and added again or its feed renamed its events, are now reconnected by start time and title, and the notes that cannot be reconnected are reported as one problem instead of one per note.

  • Reconnected by start time and title. An Event Note is tied to its event by the calendar it came from and the event's iCal UID. Removing a calendar and adding it again, changing its URL to a feed with other UIDs, or a feed that gives its events new UIDs used to leave every such note without an event. A scan now gives such a note to the event in a current calendar that has the same start, the same all-day setting, and the same title. The note's text and other properties are not changed; its event_id, source, ical_uid, and recurrence_id are rewritten, its Daily Note entry stays, and its times follow the new event unless you had changed them yourself. No message is shown.
  • Only when there is no doubt. A note is reconnected only if exactly one event without a note matches it and no other lost note matches that event. Titles are compared exactly, apart from leading, trailing, and repeated spaces; the end time is not compared. Two events with the same start and title, two notes for one event, or an event that already has a note are left for you to decide.
  • A note whose event left the feed. A note whose event the feed stopped listing is reconnected in the same way when the feed lists the same start and title under a new UID. With no such event, the note stays as it was.
  • One problem instead of many. Notes that cannot be reconnected are grouped: one problem for the notes a removed calendar left, and one for each calendar that no longer lists its notes' events. Review Event Note problems lists the notes of a group with their events, and Keep all as ordinary notes or Move all to trash applies to the whole group; open a note from the list to handle it by itself. A single such note is reported as before. The problem count in settings and in the toolbar counts problems, so a group counts once.

A note that matches an event by UID behaves as before. There is no fuzzy matching and no new setting.

Install

Download the Event Notes 0.3.8 ZIP, extract it, and copy the event-notes folder into <Vault>/.obsidian/plugins/, or install through BRAT. Moving from Calendar Pro is covered in the installation guide.

Compatibility and verification

Requires Obsidian 1.14.5 or later on desktop. npm run typecheck, npm test, and npm run package pass. Matching notes to events, reconnecting a note with its link, path claim and own times, the cases that are left alone, and the grouped problems have automated coverage. Reconnecting after a calendar is set up again in a real Vault, and the grouped problem card with its two buttons, have not had native QA in Obsidian.