-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add relationship-write support #62
Comments
Can we park this issue for now. This behaviour is only required to test the concept, not the implementation in the core API (a test for that is that the enums exist). |
Adding a little more context:
|
Probably part of #88 Closing however as this isn't neccesarily the way we want BAL, or any manager, to behave. It's certain a way it could behave, but not the canonical way, so we don't need to prioritise explicit support. |
OpenAssetIO/OpenAssetIO#1016 (comment)
Currently BAL when registering dosen't do the check where it sees if the Traitsets are the same, and then branches to either do a new version if they are, or a new entity if they are not.
This is behaviour allows us to demonstrate the canonical behaviour defined by OpenAssetIO/OpenAssetIO#1016.
To do this, we'll need some sort of relationship trait to create a relationship when a new entity is made. We've been planning to integrate mediacreation with bal anyway (See #49), so we can use the mediacreation
Relationship
trait for this.ACs
When
register
is called against an entityRef that already exists:Relationship
trait.The text was updated successfully, but these errors were encountered: