fix: added suspense and error boundary for apple pay and google pay in tabs #632
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
ArushKapoorJuspay
requested review from
seekshiva and
PritishBudhiraja
as code owners
|
Review changes with SemanticDiff. |
PritishBudhiraja
approved these changes
Sep 20, 2024
PritishBudhiraja
added
the
Ready for Review
seekshiva
approved these changes
Sep 20, 2024
github-actions
bot
added
Closed
akash-c-k
pushed a commit
that referenced
this pull request
Sep 20, 2024
## [0.88.3](v0.88.2...v0.88.3) (2024-09-20) ### Bug Fixes * added suspense and error boundary for apple pay and google pay in tabs ([#632](#632)) ([209f8e9](209f8e9))
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.
Type of Change
Description
Added Suspense and Error Boundary for ApplePay and GooglePay
How did you test it?
Test ApplePay and GooglePay in tabs flow
Checklist
npm run re:build