This is more of a feature request than a bug, and is the only thing preventing Groot from doing exactly what my App needs. As it stands all relationships are treated as complete/perfect relationships, which is not always the case.
Feature:
Be able to set an annotation on a relationship that flags it to not override existing relationships but instead merge them.
For example, my situation requires that certain objects be attached to the current logged in User object. These objects may already be attached to another User and as such need to retain that relationship post mapping.
I have been trying to work on my own fork to get this to work, and so far have had no success.
This is more of a feature request than a bug, and is the only thing preventing Groot from doing exactly what my App needs. As it stands all relationships are treated as complete/perfect relationships, which is not always the case.
Feature:
Be able to set an annotation on a relationship that flags it to not override existing relationships but instead merge them.
For example, my situation requires that certain objects be attached to the current logged in User object. These objects may already be attached to another User and as such need to retain that relationship post mapping.
I have been trying to work on my own fork to get this to work, and so far have had no success.