Refine task description and sorting order

Updated task structure and sorting logic in PLAN.md.
This commit is contained in:
SteelDynamite 2025-11-03 13:07:03 -08:00 committed by GitHub
parent f472ed5f57
commit f51d1251bb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -71,8 +71,6 @@ Task description and notes go here in **markdown** format.
- Links, etc. - Links, etc.
``` ```
**Note**: No `position` field in frontmatter - task ordering is stored in the list's `.listdata.json` file. This means reordering tasks only requires updating one file.
**TaskStatus values**: **TaskStatus values**:
- `backlog` - Task not yet completed - `backlog` - Task not yet completed
- `completed` - Task is done - `completed` - Task is done
@ -82,7 +80,7 @@ Task description and notes go here in **markdown** format.
Task { Task {
id: Uuid, id: Uuid,
title: String, // Derived from filename title: String, // Derived from filename
notes: String, // Markdown content description: String, // Markdown content
status: TaskStatus, // Backlog or Completed status: TaskStatus, // Backlog or Completed
due_date: Option<DateTime>, due_date: Option<DateTime>,
created_at: DateTime, created_at: DateTime,
@ -106,7 +104,7 @@ TaskList {
enum SortOrder { enum SortOrder {
Manual, // Use task_order from .listdata.json Manual, // Use task_order from .listdata.json
ByDueDate, // Sort by due_date field (tasks without due dates at end) ByDueDate, // Group by due_date, then sort by task_order within groups
} }
AppConfig { AppConfig {