Clarify sort order options and benefits in PLAN.md

Updated sort order explanation and benefits in PLAN.md.
This commit is contained in:
SteelDynamite 2025-11-03 13:21:47 -08:00 committed by GitHub
parent e1b46198bb
commit cb0f7692ab
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -155,14 +155,7 @@ AppConfig {
- `"manual"` - Tasks ordered by hand (uses `task_order` array) - `"manual"` - Tasks ordered by hand (uses `task_order` array)
- `"by_due_date"` - Tasks automatically sorted by due date (tasks without due dates appear at end) - `"by_due_date"` - Tasks automatically sorted by due date (tasks without due dates appear at end)
When `sort_order` is `"manual"`, the `task_order` array defines the sequence. When `sort_order` is `"by_due_date"`, tasks are sorted dynamically and `task_order` is ignored. When `sort_order` is `"manual"`, the `task_order` array defines the sequence. When `sort_order` is `"by_due_date"`, tasks are grouped first and then sorted within each group by `task_order`.
**Benefits**:
- **Two sort modes**: Manual ordering or automatic by due date
- **Ordering in list metadata**: Changing manual order only touches `.listdata.json`
- **Portable lists**: Copy/move a list folder and its metadata stays with it
- **Clean structure**: No nested hidden folders, just hidden files
- **WebDAV-friendly**: Syncing a list syncs its metadata naturally
**App Configuration** (separate from task data): **App Configuration** (separate from task data):
- Windows: `%APPDATA%/bevy-tasks/config.json` - Windows: `%APPDATA%/bevy-tasks/config.json`