connection token error handling #86
Merged
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
jdivock-stripe
approved these changes
Feb 22, 2022
arekkubaczkowski
added a commit
to arekkubaczkowski/stripe-terminal-react-native
that referenced
this pull request
Jun 29, 2022
* chore: connection token error handling * chore: init module refactor * handle init error * chore: log error * fix: ts errors * fix: variable name
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.
Add error handling for tokenProvider method.
Moreover, the error has been passed to the
setTokenProvidercompletion block so if user will try to run any method that needs a connection token it will throw a proper error message.Additionally, to give a more control of initializing the library,
initializemethod now must be called manually and independently ofStripeTerminalProvidercomponent.closes #26
closes #35