M20-I01: Task compose + dual-write #51
Labels
No labels
@Claudian
@Eliana
@Hermes
@JMax
@Kathryn
@LRM
@Nova
@Sarah-Lin
@Sylvia
@Vincent
priority:high
priority:low
priority:medium
stage:seed
task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
n8k99/dragonpunkos#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
✅ Task compose + dual-write
Port
new-task-append.py's logic to Rust: compose an Obsidian-Tasks line(
- [ ] desc [[project]] 📅 due 🔁 recur ➕ created) with flexible due parsing(
today/tomorrow/+3d/+2w/fri/next fri/ISO). Dual-write: thedue-date Daily Note's
## 📋 Tasksand the current note's## 🚀 Tasks Created Today(via➕ created). Due-less tasks → current note only.Acceptance
Compose + parse covered by tests (each due form); dual-write hits both notes
(creating sections if absent); due-less writes only today. See
M20-Events-And-Tasks · ref
new-task-append.py.