-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Card Single Result Object #841
Merged
Merged
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
b51ef9d
Add CardResult
sarahkoop 4d3e700
Fix unit tests
sarahkoop 5de9631
Fix integration tests
sarahkoop afe37b8
Fix lint
sarahkoop 200a179
Add CHANGELOG and migration guide
sarahkoop b74af56
Merge branch 'v5' into card_single_result
sarahkoop d604342
Cleanup code snippet
sarahkoop 191851b
Fix integration tests
sarahkoop 54ce6fb
Merge branch 'v5' into card_single_result
sarahkoop File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
17 changes: 17 additions & 0 deletions
17
Card/src/main/java/com/braintreepayments/api/CardResult.kt
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
package com.braintreepayments.api | ||
|
||
/** | ||
* Result of tokenizing a [Card] | ||
*/ | ||
sealed class CardResult { | ||
|
||
/** | ||
* The card tokenization completed successfully. This [nonce] should be sent to your server. | ||
*/ | ||
class Success(val nonce: CardNonce) : CardResult() | ||
|
||
/** | ||
* There was an [error] during card tokenization. | ||
*/ | ||
class Failure(val error: Exception) : CardResult() | ||
} |
7 changes: 2 additions & 5 deletions
7
Card/src/main/java/com/braintreepayments/api/CardTokenizeCallback.java
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,12 @@ | ||
package com.braintreepayments.api; | ||
|
||
import androidx.annotation.Nullable; | ||
|
||
/** | ||
* Callback for receiving result of {@link CardClient#tokenize(Card, CardTokenizeCallback)}. | ||
*/ | ||
public interface CardTokenizeCallback { | ||
|
||
/** | ||
* @param cardNonce {@link CardNonce} | ||
* @param error an exception that occurred while tokenizing card | ||
* @param cardResult a {@link CardResult} containing a {@link CardNonce} or {@link Exception} | ||
*/ | ||
void onResult(@Nullable CardNonce cardNonce, @Nullable Exception error); | ||
void onCardResult(CardResult cardResult); | ||
} |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we feel like it'd be helpful to merchants to know what the change is to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we are pretty much changing the parameters of every public method and callback throughout the SDK for this version, I've just been saying "change parameters" to keep the CHANGELOG less verbose. The detailed changes are in the migration guide though. So I don't know because yes it might be helpful to see the actual parameter changes, but also for every method that is changing the CHANGELOG will get very long and verbose. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to leave the generic parameters CHANGELOG notes for now but will reconsider how detailed we are for all of the changes in the CHANGELOG before the first beta
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think we were pretty verbose in the iOS changelog, it's quite long for the betas. No idea if it's helpful or not though.