Uh oh!
There was an error while loading. Please reload this page.
feat(elements): Support SignIn.Captcha and sso-callback step - #4523
Conversation
🦋 Changeset detectedLatest commit: 3f5b954 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| signInForceRedirectUrl: ClerkJSNavigationEvent.complete, | ||
| signInFallbackRedirectUrl: ClerkJSNavigationEvent.complete, | ||
| signUpForceRedirectUrl: ClerkJSNavigationEvent.complete, | ||
| signUpFallbackRedirectUrl: ClerkJSNavigationEvent.complete, |
There was a problem hiding this comment.
Now that we're not passing beforeEmit to setActive internally, our custom navigate hackery wasn't working as intended here. Removing the URLs allows navigate to complete.
There was a problem hiding this comment.
Does this mean we broke the usage of handleRedirectCallback for everyone ?
There was a problem hiding this comment.
Hey, trying to use <SignIn.Captcha /> but I see Property 'Captcha' does not exist ....
I believe you forgot to export this component in index.ts right?
There was a problem hiding this comment.
@corentinmusard yes, good catch. PR here #4548
Description
Introduces support for
<SignIn.Captcha>as well as<SignIn.Step name='sso-callback'>. This allows rendering of the CAPTCHA widget when a sign in flow is transferred to a sign up flow.Also fixes a bug with the SSO callback where a successful auth would navigate to the incorrect URL. This was due to a recent change that switched to passing a URL directly to
setActive(), instead ofbeforeEmit.Checklist
npm testruns as expected.npm run buildruns as expected.Type of change