-
Notifications
You must be signed in to change notification settings - Fork 124
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
Parsing for relationships is confusing #552
Comments
Note that this issue has relevance to both the new design for Concerto relationships / identified classes (see Issue accordproject/concerto#181) and to the new parser (see Issue #547). With the current development code for the new parser, we get:
|
I think this behaviour is correct. It is much more explicit and the URI scheme for the relationship allows the caller to retrieve the instance type and the id. |
This issue has been fixed using the new parser infrastructure and is fixed in the development version of Cicero. |
Parsing for complex variables which are relationships is confusing.
cicero parse
for variables involved in a relationships (https://templates.accordproject.org/[email protected])shipper
andreceiver
are not of typeString
but of type--> Organization
. It is not easy to determine from the output. Also the content of the organization is not available to the runtime.For reference the model is:
The text was updated successfully, but these errors were encountered: