Conversation
Resolve the nearest shallower checkbox during native task creation, inherit its project, and preserve the remote parent relationship locally. Reject unsynced parents and conflicting project markers, with coverage for spaces, tabs, blockquotes, and API responses.
kairan0
marked this pull request as ready for review
September 15, 2026 15:10
Owner
|
tomorrow I will review the PR and merge |
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.
Fixes #34
Summary
parentId, inherit its project, and persist the server-confirmed placement locally.Safety boundary
This only affects the explicit Insert/create Dida task action for an unlinked Markdown checkbox. Editing the indentation of an already linked task does not reparent or unparent the remote task, because the same task can be referenced from multiple notes.
Testing
npm testnpm run buildgit diff --checkThe repository-wide
npx tsc --noEmitcommand still reports pre-existing Electron, Obsidian, and test typing errors; none point to the new production code.