style(time): apply rustfmt to TimeEntryEditModal work_type signal #160
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/mapps-183-time-rustfmt"
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?
The use_signal closure initialising the work_type signal in
TimeEntryEditModal exceeded the line-width limit, so cargo fmt --check
failed in check.yml. Reformat the closure across multiple lines to
match rustfmt output and restore a green fmt step.
#MAPPS-183
MAPPS-166. Time entries were read-only on the list (the server already supports PUT/DELETE /time-entries/{id}). Make list rows click-to-edit, opening a modal that edits the common fields - work type, hours, date, description, billable - plus delete. The modal reuses the server's update endpoint. Because that PUT direct-sets ticket_id/project_id/task_id (no COALESCE) and never recomputes company_id, the edit form intentionally keeps the work item and task fixed and re-sends their ids so a partial-looking update does not null them; to move an entry to a different work item, delete it and log again. RemoteTimeEntry gains id/work_type_id/task_id (and PartialEq) so a row can be edited. Not compiled locally (no Rust toolchain in this environment); mirrors the existing Log Time form and the task/rate-card edit modals, and is gated by CI (cargo clippy --all-targets -- -D warnings). #MAPPS-166 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>