-
Notifications
You must be signed in to change notification settings - Fork 72
Update the progressive parameter in the KYC session creation API to use a boolean type #10632
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
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.27 MB ℹ️ View Unchanged
|
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.
That makes sense to me, @mordeth !
This change will be released on Apr, 9 so I guess that we should be good when it's used in WC Core 9.9.
However, if the old version of WooPayments is installed (that uses string), then it might be an issue. Will Core handle this BC nuance?
Great question, Oleks! The In-context onboarding will only be available for new stores without onboarded accounts. If the WooPayments version is older than 9.2, we’ll fall back to the original external onboarding flow via redirect. |
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.
Noticed the latest fixes, LGTM now
Changes proposed in this Pull Request
This PR updates the type of the progressive parameter in the KYC session creation API to boolean. This change ensures compatibility with the implementation introduced in Add NOX in-context APIs, where the parameter is now expected to be a boolean value.
Testing instructions
npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge