Skip to content
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

[fact] Overhaul content conflict detection #60

Merged
merged 1 commit into from
Mar 10, 2020

Conversation

slarse
Copy link
Collaborator

@slarse slarse commented Mar 9, 2020

Fix #59

This entirely does away with the notion of primary and secondary values, and simply stores all values that are relevant as "equally important". Node content values are then handled and merged entirely separately from the rest of the merge.

This entirely does away with the notion of primary and secondary values, and simply stores all values that are relevant as "equally important"
@slarse slarse merged commit 0f835a6 into master Mar 10, 2020
@slarse slarse deleted the issue/59-refactor-content-handling branch March 15, 2020 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor content handling to not have a notion of primary/secondary values
1 participant