docs(intent): locksWithMaster - a child collection that outlives its master's lock - #172
Merged
Merged
Conversation
…master's lock A master's immutableWhen locks that entity, but the generated UI extended the lock to every child PANEL, so an issued invoice's allocation rows could not be added by hand - in the one state where allocations matter. The child's own controller always accepted the writes. Documents locksWithMaster: false, its default, the two parse-time validations, and the boundary: a document's own line items are unaffected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
A master's
immutableWhenlocks that entity, but the generated UI extended the lock to every child panel — so an issued invoice's allocation rows could not be added by hand, in the one state where allocations matter. The child's own controller always accepted the writes (verified live: mastermutable:falseand a header PUT 409, while a POST to the child returned 200 and the roll-up recomputed).Documents
locksWithMaster: false, its default (true), the two parse-time validations (composition child + a master that actually locks), and the boundary: a document's own line items are unaffected — they render in the items pane, not a child panel.Feature: eclipse-dirigible/dirigible#6700.
🤖 Generated with Claude Code