docs(intent): personalReadOnly is declarable on a composition edge too (#7340) - #243
Merged
Conversation
…o (#7340) The key closed a whole personal surface or nothing, and a composition child cannot carry `personal:` at all, so a header the owner authors whose lines an engine writes had no expressible shape - the child was writable exactly when its parent was. On the composition relation it closes only the child's inherited surface: the child's MyController answers 403 and the parent's my/document page drops the items Add, the row actions and that child panel's Add, while the header keeps Save and Delete. 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.
Documents eclipse-dirigible/dirigible#7354.
The DSL reference said
personalReadOnlygoes withpersonal: trueand that composition children inherit it through the parent. That coupling left the commonest personal-surface shape unexpressible: a header the owner authors whose lines an engine writes (a leave request whose day rows the approval flow charges against an entitlement) - the child was writable exactly when the header was, so the generated child MyController accepted a create from the owner's own draft against any entitlement in the tenant.The paragraph now covers both ends: alongside
personal: trueit closes the declaring entity's own surface, and on a composition relation it closes only that child's inherited surface while the parent stays writable - with the effect on the generated pages and the cases where the key is refused.npm run docs:buildpasses.🤖 Generated with Claude Code