We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Changes don't sync when using XStore Association Mapping.
Workspace should sync without any unsynced file
Use this code
Class model::MapPerson { firstName: String[1]; } Class model::MapFirm { firstName: String[1]; } Class model::Person { firstName: String[1]; lastName: String[1]; } Class model::Firm { legalName: String[1]; } Association model::FirmPerson { firm: model::Firm[1]; employee: model::Person[1]; } ###Mapping Mapping model::NewMapping ( *model::Firm[firm]: Pure { ~src model::MapPerson legalName*: $src.firstName } *model::Person[person]: Pure { ~src model::MapFirm firstName: $src.firstName } model::FirmPerson: XStore { firm[person, firm]: $that.legalName == $this.firstName } )
This could be a hashing issue.
The text was updated successfully, but these errors were encountered:
legend-studio/packages/legend-graph/src/models/metamodels/pure/packageableElements/domain/PropertyReference.ts
Line 74 in a05f475
legend-studio/packages/legend-graph/src/models/protocols/pure/v1/model/packageableElements/domain/V1_PropertyPointer.ts
Line 31 in a05f475
These two lines are the issue. on the line 31 of v1 property pointer, value of this.class comes out to be the correct model::FirmPerson
model::FirmPerson
and on the line 74 in PropertyReferenc.ts the value for this.ownerReference.hashValue this comes out to be model::Person
this.ownerReference.hashValue
model::Person
also this following comment mentions this property to be implicit:
legend-studio/packages/legend-graph/src/models/protocols/pure/v1/transformation/pureGraph/to/V1_ProtocolToMetaModelPropertyMappingBuilder.ts
Line 753 in a05f475
Sorry, something went wrong.
MauricioUyaguari
Successfully merging a pull request may close this issue.
🐛 Bug Report
Changes don't sync when using XStore Association Mapping.
Expected behavior
Workspace should sync without any unsynced file
Reproduction Code or Repo
Use this code
Possible Solution
This could be a hashing issue.
Additional context
The text was updated successfully, but these errors were encountered: