[1.x] fix: use orphan parameter when creating token - #141
Merged
Conversation
The createToken() method with explicit "orphan" argument always creates an orphan token, while providing false explicitly should be effectively the same as the method without any argument. Handle the argument properly and use the correct endpoint when false. (backported from commit 413ac24)
|
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
1 participant
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.
Backport of #140 to v1
The
createToken()method with explicitorphanargument always creates an orphan token, while providingfalseexplicitly should be effectively the same as the method without any argument.Handle the argument properly and use the correct endpoint when false.
(backported from commit 413ac24)