Add support for arbitrary conflict resolutions #101
Merged
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.
The user can provide an arbitrary number of features in a geojson file, and store them as the resolution to a conflict. Generally, the appropriate number of features will be either 1 - in the case of an edit/edit conflict that needs manual resolution - or 2, in the case of an add/add conflict, the resolution should probably contain both features in some form. (Zero is also a useful number of features, but it is already possible to resolve a conflict by supplying zero features without providing a file).