-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Location differs for choice elements between ITypedElement adapters on POCO and SourceNode #2642
Comments
This turns out to be by design. Location can differ between implementations. |
@mmsmits Do you propose that we implement some sort of workaround in FS for the original issue? |
@alexzautke, I did not know this was originally an issue for FS. |
@mmsmits The context was lost between Slack and creating the issue. In FS we rely on MaskingNode for the implementation of _elements. In FS the location always comes from a SourceNode. That’s why it currently fails on choice types. See https://firelyteam.slack.com/archives/C011XD1TKL0/p1703004394364199 |
Reopened by request of the Firely Server team, but not urgent |
We discovered that TypedElementOnSourceNode and PocoElementNode produce different locations for children that are choice types:
Since the
MaskingNode
is depending on the Location to do its work, generating a summary using the MaskingNode only works well on POCO-based models but not on SourceNode-based models.The text was updated successfully, but these errors were encountered: