fix incorrect JNI signature for PatchAction.FlagConflict constructor #15
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.
When I do something like the following for an Automerge
Document
object called_doc
withSyncState
called_syncState
:I get the following panic if there are any
PatchAction.FlagConflict
actions among the patches:I believe this PR fixes that problem. The JNI signature to call the Java
FlagConflict
constructor from Rust was incorrect: there should only be 1 argument (theProp
), not 2.