fix: sdk button redirect issue #398
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
PritishBudhiraja
added
the
Ready for Review
prafulkoppalkar
approved these changes
May 23, 2024
ArushKapoorJuspay
approved these changes
May 23, 2024
github-actions
bot
added
the
Closed
akash-c-k
pushed a commit
that referenced
this pull request
May 23, 2024
## [0.54.2](v0.54.1...v0.54.2) (2024-05-23) ### Bug Fixes * sdk button redirect issue ([#398](#398)) ([dd78d56](dd78d56))
rising-dragon401
added a commit
to rising-dragon401/hyperswitch-web
that referenced
this pull request
Jul 2, 2024
## [0.54.2](juspay/hyperswitch-web@v0.54.1...v0.54.2) (2024-05-23) ### Bug Fixes * sdk button redirect issue ([#398](juspay/hyperswitch-web#398)) ([dd78d56](juspay/hyperswitch-web@dd78d56))
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
Fix for redirect as it was been passed in wrong place
How did you test it?
Via passing redirect = always and checking the redirection
Checklist
npm run re:build