Jean-Luc Makiola
e0c56a73e2
All checks were successful
CI / ci (push) Successful in 6m49s
M3 detail/edit polish: - "Progress" slider on the edit form writes Tasks.PERCENT_COMPLETE (clamped 0-100, 5% detents); status stays owned by the complete toggle. - Conflict-safe saves: updateTask re-checks the provider's last_modified against the value captured when the form loaded and throws TaskConflictException; the editor offers overwrite-or-cancel instead of clobbering an external change. M4 subtasks (UI): - Reparent: a "Parent task" picker files a task under any top-level task in its list (or "None" to promote it); candidates stay top-level to keep nesting one level deep. Switching list clears the now-invalid parent. - Tapping a subtask opens its own detail (a new TaskDetail entry, own VM). Tests: percent clamping, parent-id write, populatedFields reveal logic. Docs: ROADMAP M2/M3/M4 reconciled to the codebase; CHANGELOG [Unreleased]. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
3.0 KiB
3.0 KiB
Changelog
All notable changes to this project are documented here. The format follows
Keep a Changelog; the latest released git tag is
the source of truth for version codes (see Calendula's docs/RELEASING.md).
[Unreleased]
Added
- M3 detail/edit polish: a "Progress" slider (percent-complete, 5% detents,
written to
Tasks.PERCENT_COMPLETE) and conflict-safe saves —updateTaskre-checks the provider'slast_modifiedagainst the value captured when the form loaded and surfaces an overwrite-or-cancel prompt instead of clobbering an external change (e.g. a DAVx5 sync). - M4 subtasks (UI): reparent — a full-width, searchable "Parent task" sheet on the edit form, with candidates grouped by due-date section, files a task under any active top-level task in its list (or "None" to promote it); switching list clears the now-invalid parent. Tapping a subtask in the detail screen opens its own detail, which shows a "Part of …" parent card. On the task list a parent has a dedicated expand button that reveals its children as a nested grouped run, ending with an inline "add a subtask" row (an opt-out toggle is planned for the M6 settings screen).
- Priority is coloured by level (green / amber / red pastels) on the list, detail, and edit screens.
Fixed
- Overview open-counts now count top-level tasks only, so subtasks — and especially open subtasks under a completed parent — no longer inflate a list's "N open" or the smart-list counts.
- Swipe-to-delete now reveals its red background + icon as you drag (tracking the live direction, not just the settled target), and a floating "Deleted · Undo" chip defers the actual delete so it can be restored.
[0.1.0] - 2026-06-18
Added
- M1 data layer + logic ("backoffice"): the full non-visual stack over the
OpenTasks
TaskContractprovider (authority resolved at runtime —org.tasks.opentasksfor tasks.org,org.dmfs.tasksfor OpenTasks).- Vendored
TaskContractsubset,ProviderResolver,ColumnReader, mappers,AndroidTasksDataSource(Instances query + ContentObserver), andTasksRepositoryexposing live Flows of lists/tasks/detail. - Domain models, smart-list filtering (Today/Upcoming/Overdue/No-date/All/
Completed), sorting, form validation, sub-tasks via
parent_id. - Self-scheduled due-reminder engine (AlarmManager + boot/provider-change re-sync), notifications, DataStore prefs.
- Render-only ViewModels + UiState for every screen (lists, task list, detail, edit, settings, permission) so the UI is build-only.
- 24 JVM unit tests (mappers, filtering, sorting, form, value mapping, day
windows).
RootScreenis a functional scaffold over the real data, to be replaced screen-by-screen with the Material 3 Expressive design.
- Vendored
- M0 skeleton: project scaffolding copied from Calendula (Gradle, version catalog, Hilt, Material 3 Expressive theme, Gitea CI/release workflows), reseeded to a warm-mauve palette. Builds and shows a themed placeholder.