Fixes in Java's User Propagator#7088
Merged
Merged
Conversation
- Added return value to conflict - Added consequence method - Added missing access modifier to decideWrapper
Contributor
Author
|
@microsoft-github-policy-service agree |
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.
decideWrappermethod toUserPropagatorBase.javadecidecallback correctly since it's signature change from Fix UP's decide callback #6707Native.propagateConflictto return a boolean success value and renamed it toNative.propagateConsequence.UserPropagatorBase.consequenceto allow propagation of consequences.UserPropagatorBase.javaNote: I have not tested any changes