Skip to content

make ui compatible with new single task lock functionality - #2899

Open
CollinBeczak wants to merge 7 commits into
v4from
collin/lock-conflict-modal
Open

make ui compatible with new single task lock functionality#2899
CollinBeczak wants to merge 7 commits into
v4from
collin/lock-conflict-modal

Conversation

@CollinBeczak

@CollinBeczak CollinBeczak commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

This pr also includes some other miscellaneous work due to me debugging issues as i found them when getting the ui to work properly. Will keep future pr's more focused.

The backend now allows a user only one active task lock at a time and
returns 409 with the held lock's details when a second lock attempt
conflicts. Add getLockConflict to parse that response and a
useLockConflict hook that shows LockConflictModal, releases the held
task via the existing unlock endpoint, and retries the original
action on confirm. Wire it into TaskContext's auto-lock/manual lock
and into TaskActionModal's bundle create/update flow, and add
bundledTasks to the LockedTaskData type.
…xt lock-clearing

Dedupe the repeated navigate({ to: '/tasks/$taskId', ... claimTask: true }) call across
task-start/skip/nearby/random navigation and the lock-conflict dialog into a single
useNavigateToTask hook. Also collapse the three near-identical inline lock-clearing
callbacks in TaskContext into one clearLockState helper.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant