forms: a relation.field may cross models - #69
Open
delchev wants to merge 1 commit into
Open
Conversation
The spec described a form's relation.field as a one-hop to-one without saying which models the hop may reach, and implementations read that as local-only - so the relation a document's form most needs to read a field of, its counterparty, was refused. State it: the hop may be cross-model, resolved against the owner's model at generation time, the same one-hop path a notify recipient takes, and a field the owner does not declare must be reported rather than silently dropped. 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.
The
formssection described arelation.fieldentry as a one-hop to-one path without saying which models the hop may reach — and implementations read that as local-only, so the relation a document's form most needs to read a field of, its counterparty, was the one it refused (an invoice's Send form showing the customer's address). The same one-hop path is already cross-model for anotifyrecipient.This states it, in the shape the cross-model roll-up paragraph already uses:
model:must be declared inuses:;Implemented in Eclipse Dirigible: eclipse-dirigible/dirigible#7118 (issue eclipse-dirigible/dirigible#7093).