Stream: conformance
Topic: Forge - Expand common elements
Jonny Rylands (Apr 06 2016 at 16:04):
@Michel Rutten Think I've spotted a bug in Forge - if you create a profile that modifies one of the common elements (e.g. change cardinality of id element), then open in Forge with the "Expand common elements" turned off - I get the following error:
Unexpected ElementDefinition at index 3 with path '<ResourceName>.identifier.use' from basePath = '<ResourceName>'
Turning "Expand common elements" back allows you to open the profile OK.
Michel Rutten (Apr 07 2016 at 08:22):
@Jonny Rylands thank you for the bug report! I will investigate the issue.
Michel Rutten (Apr 07 2016 at 09:13):
@Jonny Rylands I can reproduce and confirm the reported issue.
Because the common resource elements may be confusing for some users, I tried to make this behavior configurable. Your bugreport demonstrates that I cut one corner too many. To deal with this, I think that Forge always has to expand the full snapshot, including elements inherited from the abstract (Domain)Resource base class. Then I can re-implement the configuration setting as a visibility toggle that shows/hides the common elements. I'll try this now, stay tuned.
Jonny Rylands (Apr 07 2016 at 10:08):
OK thanks. Or even a message to say that you need to open the profile with the common elements setting enabled?
Michel Rutten (Apr 07 2016 at 11:02):
Nah, I'd rather not bother the user, unless strictly necessary. Looks like I can solve this elegantly via a global visibility toggle. Stay tuned...
Last updated: Apr 12 2022 at 19:14 UTC
