add compatibility with new single task lock restriction and endpoints - #2898
Draft
CollinBeczak wants to merge 1 commit into
Draft
add compatibility with new single task lock restriction and endpoints#2898CollinBeczak wants to merge 1 commit into
CollinBeczak wants to merge 1 commit into
Conversation
The backend now enforces one active edit lock per user and locks a task bundle as a single row on its primary task instead of one row per member, which had silently broken bundle creation here (it called the now-removed bulk lock endpoint) and left 409 lock conflicts with no dedicated UI. Replaces per-task bundle locking/refreshing with a single lockTaskBundle call representing the bundle's full desired membership, and adds a release-conflicting-lock-and-retry flow to both the single-task and bundle-lock dialogs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The backend now enforces one active edit lock per user and locks a task bundle as a single row on its primary task instead of one row per member, which had silently broken bundle creation here (it called the now-removed bulk lock endpoint) and left 409 lock conflicts with no dedicated UI.
Replaces per-task bundle locking/refreshing with a single lockTaskBundle call representing the bundle's full desired membership, and adds a release-conflicting-lock-and-retry flow to both the single-task and bundle-lock dialogs.