You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.
Let's assume these relationships were used in a view "V" coming from B, but remove since
We merge again B into A with "update" option not set
"V" should be restored (because this is a merge and "V" no more exist), but "V" contains a relationhip whose ends have changed, so this relationiship can no more exist in "V"
So in fact we can't restore "V"
What do we do? Either we abort the whole merge operation because we can't merge/restore "V" exactly as it was in B, or we raise a warning?
From my tests, as of now, running this tests end up with the view being imported and the relationship ends moved back to their original elements (ie. relationship has been updated while update mode is off). I can confirm that relationship is not updated if no views from B contain it (expected behavior).
My thoughts:
This behavior is somewhat aligned with what we have in coArchi (ie. restore some deleted object after a merge if this is needed to keep the model coherent).
This should be logged as "Some relationships were forced-updated during the import of some views" and shown in a small dialog box at the end of the import operation
In an ideal world, this "summary" dialog box should allow me to see the detailed log (which relationships' type, name and ends)
Edge case 2
Model B as already been imported into A
Some relationship's ends has been changed
Let's assume these relationships were used in a view "V" which does not come from B (ie. created after the first merge)
We merge again B into A with "update" option set
Because "update" option is set, the relationship is restored to its original ends.
"V" is impacted because now the relationship is no more valid in the context of the view
What do we do? Warning?
Tested, and of course, "V" is impacted as expected.
My thoughts:
This should be logged as "Some local views were updated during the import of some relationships" and shown in a small dialog box at the end of the import operation
In an ideal world, this "summary" dialog box should allow me to see the detailed log (which views and why)
In addition:
A "summary" dialog could provide the number of elements, relationships, views and folders imported, updated...
A detailed log could also provide the full list of elements, relationships, views and folders imported, updated... and whether they were existing or not.
From my tests, as of now, running this tests end up with the view being imported and the relationship ends moved back to their original elements (ie. relationship has been updated while update mode is off). I can confirm that relationship is not updated if no views from B contain it (expected behavior).
My thoughts:
Tested, and of course, "V" is impacted as expected.
My thoughts:
In addition:
Originally posted by @jbsarrodie in #1 (comment)
The text was updated successfully, but these errors were encountered: