-
Notifications
You must be signed in to change notification settings - Fork 32
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
SO-4901: identical component conflict #1160
Conversation
...use cases 1. added vs added with same object key and values (should not be reported as conflict) 2. added vs added with same object key but different values (still conflict)
...there is only one present on each side of the merge
...added vs added conflict is detected and ensure we only report conflict for objects with different properties
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## 8.x #1160 +/- ##
============================================
- Coverage 64.07% 64.05% -0.02%
- Complexity 12771 12778 +7
============================================
Files 1763 1763
Lines 59596 59628 +32
Branches 5496 5508 +12
============================================
+ Hits 38184 38197 +13
- Misses 19042 19058 +16
- Partials 2370 2373 +3
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍏
This PR improves the automatic conflict resolution to allow identical objects to be added to both sides of the merge. This earlier resulted in a conflict now it passes through.