Repository navigation
Shared Tasks 0.4.2
Shared Tasks 0.4.2: a fix for a Task edit in a shared section that could be
lost without a warning. Update soon.
Requires Obsidian 1.13.4 or later, as 0.4.1.
Fixes
- A Task edited in a copy of a shared section could be silently lost.
When a shared section was copied into another note, or a note was
opened without its sync record on this device, a change made there to a
Task alone (its title, its checkbox, a date) was taken as the shared
version.
The next sync then wrote the shared Task back over the line: the edit
disappeared and nothing was sent. 0.4.2 compares each Task's fields too.
When they differ, your text stays as it is and the section waits for your
choice; when the note shows the shared version (only the formatting
differs), it syncs as before. - Repair lists every section that waits for a choice. "Repair shared
sections in this note" now lists such a section and shows both versions.
"Share my version" sends the note's Task fields; "Use the shared version"
shows the shared one and keeps your text as a recovery copy on this
device. If a Task in the section is still loading, is not a valid task in
the shared version, or was deleted there, Repair says so, and "Share my
version" keeps your text as it is without guessing.
Known limits
- A Task or a paragraph pasted into a section that already syncs, where
this device's sync record does not know that line yet, can still be
replaced by the shared version on the next sync. This is rare (for
example, pasting a line copied from another note of the same section);
a fix is planned for 0.5.0
(#41).
Under the hood
- The TypeScript SDK stays
@openlfcp/*0.2.1; specmvp-0.2-baseline.12;
the project server runs the reference server 0.3.2, unchanged by this
release. - Unit tests cover each Task field, a copied section, a Task not loaded
yet, a conflicted title and a formatting-only difference; a live test with
the plugin on the reference server keeps a Task title edited in a copied
section across a restart.
Install and upgrade
From Community plugins (Settings → Community plugins → Updates), with BRAT
(openlfcp/obsidian), or by hand: put main.js, manifest.json and
styles.css from the release page into
<vault>/.obsidian/plugins/shared-tasks/. Your identity, collaborations and
settings are kept.