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

[fix] Handle modifiers #42

Merged
merged 3 commits into from
Mar 3, 2020
Merged

[fix] Handle modifiers #42

merged 3 commits into from
Mar 3, 2020

Conversation

slarse
Copy link
Collaborator

@slarse slarse commented Mar 3, 2020

Fix #36
Fix #39

This PR is a start for addressing the problem that some nodes have many values associated with them. It introduces the notion that there's a primary value (e.g. the name of a method or field), and secondary values (e.g. modifiers).

As conflicts related to secondary values can't be resolved during the base 3DM merge without introducing significant complexity, they are resolved after that, in the Spoon3dmMerge class. Currently, only conflicts that can be automatically resolved are handled properly. Conflicts that can't be automatically resolved will lead to the primary value being flagged as conflicting.

This means that a new way of handling content conflicts must be introduced.

Content is now a) not modified in-place, and b) retained in full on conflicts
But does not deal with conflicts!
@slarse slarse changed the title Issue/36 handle modifiers [fix] Handle modifiers Mar 3, 2020
@slarse slarse merged commit e293a1f into master Mar 3, 2020
@slarse slarse deleted the issue/36-handle-modifiers branch March 5, 2020 07:56
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 TdmMerge class to not modify contents in-place Modifiers are dropped
1 participant