Minor Changes
-
Updates related to experimental Google One Tap support (#3250) by @panteliselef
- By default we are returning back to the location where the flow started.
To accomplish that internally we will use the redirect_url query parameter to build the url.
<__experimental_GoogleOneTap />
- In the above example if there is a SIGN_UP_FORCE_REDIRECT_URL or SIGN_IN_FORCE_REDIRECT_URL set then the developer would need to pass new values as props like this
<__experimental_GoogleOneTap signInForceRedirectUrl='' signUpForceRedirectUrl='' />
- Let the developer configure the experience they want to offer. (All these values are true by default)
<__experimental_GoogleOneTap cancelOnTapOutside={false} itpSupport={false} fedCmSupport={false} />
- Moved authenticateWithGoogleOneTap to Clerk singleton
Clerk.__experimental_authenticateWithGoogleOneTap;
- Created the handleGoogleOneTapCallback in Clerk singleton
Clerk.__experimental_handleGoogleOneTapCallback;
- By default we are returning back to the location where the flow started.
-
Introduce new
client_mismatch
verification status for email link sign-in and sign-up. This error (and its message) will be shown if a verification link was opened in another device/browser from which the user initiated the sign-in/sign-up attempt. This functionality needs to be enabled in the Clerk dashboard. (#3367) by @mzhong9723
Patch Changes
-
Improve logging for CAPTCHA script loading errors (#3374) by @anagstef
-
Respect the
signInForceRedirectUrl
,signInFallbackRedirectUrl
,signUpForceRedirectUrl
andsignUpFallbackRedirectUrl
props passed toSignInButton
,SignUpButton
and the low-levelwindow.Clerk.buildSignInUrl
&window.Clerk.buildSignUpUrl
methods. These props allow you to control the redirect behavior of theSignIn
andSignUp
components. For more information, refer to the Custom Redirects guide. (#3361) by @nikosdouvlis -
Updated dependencies [
6f61130e3
,94197710a
,b27ca8366
,201b28d37
,b27ca8366
]:- @clerk/[email protected]
- @clerk/[email protected]
- @clerk/[email protected]