Dangerous not to have steps 2 & 3.
We really need a step 2 to confirm what we are going to get in the merge. Then a step 3 to verify. The old method of step 1,2,3 is much better. Just add the extra confirmations and/or warnings to that method please.
This new method does not allow us to detach relationships on step 2 as before. Maybe that is good, but we need some clarification on what you want us to do if there is a bad relationship to be deleted. For example, a warning to go back to the PID to be deleted and do the edits before coming back to the merge. It is harder that way, but perhaps better in the long run as it may encourage better change logs explaining just what we are doing and why.
And, for now please allow a simple switch back and forth between the methods so that we can see what we are going to get.
For now, I am going to warn most users against using this new labs version. It should be just for experienced users in my opinion.
BTW when I finished the merge it asked why I was ignoring the warning. I responded and sadly that response became the reason for the merge on the change log. PID: GZTC-CD3. This should not be the case. The reason to ignore is not the reason for the merge!
Comentários
-
@Kevin Augustus Long thank you for your feedback. We will definitely looking at these issues and suggestions :)
0 -
@Kevin Augustus Long update: a ticket has been created to look into the issues and suggestions :)
0
