forms: a relation.field may cross models - #52
Open
delchev wants to merge 1 commit into
Open
Conversation
State what the forms section left open: the one-hop hop may reach an entity another module owns, which is what lets a document's form show a field of its counterparty (an invoice's Send form showing the customer's address). Same one-hop path a notify recipient takes, checked against the owner's model at generation, and a field the owner does not declare must be reported rather than leaving a control bound to nothing. 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.
Site half of IntentFile/intent-specification#69.
The
formssection described arelation.fieldentry as a one-hop to-one without saying which models the hop may reach, so the relation a document's form most needs to read a field of — its counterparty — read as out of scope. States it: the hop may be cross-model (an invoice's Send form showing the customer's address, so the clerk sees an empty one before pressing Send), themodel:must be declared inuses:, the field is checked against the owner's model at generation, and a field the owner does not declare must be reported rather than leaving a control bound to nothing.Implemented in Eclipse Dirigible: eclipse-dirigible/dirigible#7118 (issue eclipse-dirigible/dirigible#7093).
npm run docs:buildis clean.