fix(tasks): synchronize file updates with SQLite and FTS - #230
Open
fallintoplace wants to merge 1 commit into
Open
fix(tasks): synchronize file updates with SQLite and FTS#230fallintoplace wants to merge 1 commit into
fallintoplace wants to merge 1 commit into
Conversation
fallintoplace
force-pushed
the
fix-task-update-sync
branch
2 times, most recently
from
July 30, 2026 17:58
e5e37da to
9a269c6
Compare
fallintoplace
force-pushed
the
fix-task-update-sync
branch
from
July 30, 2026 17:59
9a269c6 to
b331ab7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem
task_updaterefreshed SQLite and FTS only inside the title-update branch, before applying the remaining changes. This left three stale-state paths:Deadline sorting, escalation, the tasks UI, and search could therefore disagree with the task file until a later reindex.
Fix
The handler now applies all requested file changes first, writes the final Markdown, and then performs one upsert with the final title, status, deadline, tags, and content. Metadata-only updates keep their existing fallback path.
Tests
Regression coverage verifies deadline-only updates, note indexing, and a combined title, status, deadline, tags, and note update.