Closed elsylambert closed 1 year ago
@elsylambert Is this the issue where dcs-branch-merger is returning a false conflict?
I found that the false conflict usually happens on a bigger book (like Matthew). Specifically, this happens when the user is in the book on Gateway Edit. The change doesn't necessarily have to be in a bigger book, but if the user has navigated to a bigger book in Gateway Edit, then this issue happens.
This is just hard to test because it's MOODY
@elsylambert @danielklapp Just merged in the changes to fix false conflict on merge/update! The only thing is that there is a chance on save for the false conflict, but I can't fix that in the app unless I set a very long delay which would be undesirable. Hopefully the future changes to gitea help
Verified in v2.1.0 build 34af947 QA. Edits made to en_tn are not showing conflicts when they are made in different books. When edits are made to same book and same note, the red dot is indicated and conflict error is shown, which is the expected behaviour. Looks good.
Agree when editing two different books in en_tn, conflicts aren’t shown. Working properly in v2.1.0 build 10ae431 QA.
Update content shows conflict in en_tn when edits are made in a different book. Steps:
Conflict Error should not show for a different book.