Remove deprecated argument destinationAccount on server.strictReceivePaths. #447
Conversation
This file contains 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
abuiles
force-pushed
the
fix-strict-receive
branch
from
b0bd489
to
939ee89
Compare
morleyzhi
approved these changes
Oct 16, 2019
This was referenced Oct 16, 2019
Merged
|
Well, that was blazing fast :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We included an argument on
strictReceivePathswhich is not longer required. This updates the method to take the right arguments. Fixes #466Although this is a "breaking" change, we'll release this as a minor bump since this was just released yesterday and most of the people were using
server.pathsanyways.