[2.0] Fix conflict resolution - #374
Merged
Merged
Conversation
added 2 commits
July 15, 2014 09:14
When a public model is added to an application and the model has change tracking enabled, its Change model is added to the public models. Before this change, conflict resolution in the browser was not working, because it was not possible to fetch the remote change.
Member
|
LGTM |
Member
Author
|
Released as |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/to @ritch please review
The goal of this patch is to fix the replication for my Saturday's talk. I think it should be possible to get the conflict resolution working even without a public Change model, but I don't have time to investigate that at the moment.