Skip to content

fix(clerk-js,types): Close modals when setActive({redirectUrl}) is called#5092

Merged
panteliselef merged 20 commits into
mainfrom
elef/sdki-856-set-active-emitter
Feb 12, 2025
Merged

fix(clerk-js,types): Close modals when setActive({redirectUrl}) is called#5092
panteliselef merged 20 commits into
mainfrom
elef/sdki-856-set-active-emitter

Conversation

@panteliselef

@panteliselef panteliselef commented Feb 6, 2025

Copy link
Copy Markdown
Contributor

Description

A simpler solution to #5077 which allows the e2e test of #5071 to pass 🟢.

General Problem

Since the deprecation of setActive({ beforeEmit }), our UI components have been using Clerk.navigate in order to navigate when setActive({ redirectUrl }) is set which does no handle closing the already open modals.

Specific use-case

This buggy behaviour is clearly visible, when you attempt to delete a user from UserProfile rendered in a modal. Upon deletion, setActive({redirectUrl}) was called, but when a soft navigation occurred (using framework router) the modal would not close, and the backdrop was clearly visible.

Solution

This solution in this PR fixes the above issues while maintaining setActive simple to use for developers. We also still discourage the explicit usage of setActive({beforeEmit})

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

@panteliselef panteliselef self-assigned this Feb 6, 2025
@changeset-bot

changeset-bot Bot commented Feb 6, 2025

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 8c66b98

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 22 packages
Name Type
@clerk/clerk-react Patch
@clerk/types Minor
@clerk/clerk-js Patch
@clerk/chrome-extension Patch
@clerk/elements Patch
@clerk/clerk-expo Patch
@clerk/nextjs Patch
@clerk/react-router Patch
@clerk/remix Patch
@clerk/tanstack-start Patch
@clerk/astro Patch
@clerk/backend Patch
@clerk/expo-passkeys Patch
@clerk/express Patch
@clerk/fastify Patch
@clerk/localizations Patch
@clerk/nuxt Patch
@clerk/shared Patch
@clerk/testing Patch
@clerk/themes Patch
@clerk/ui Patch
@clerk/vue Patch

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

@vercel

vercel Bot commented Feb 6, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 12, 2025 11:54am

@panteliselef panteliselef changed the title Elef/sdki 856 set active emitter fix(clerk-js,types): Close modals when setActive({redirectUrl}) is called Feb 6, 2025
@panteliselef
panteliselef requested a review from a team February 6, 2025 17:21
@panteliselef
panteliselef marked this pull request as ready for review February 6, 2025 17:21
}
};

#resetComponentsState = () => {

@LauraBeatris LauraBeatris Feb 7, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't we still need this for custom flows that mount SignIn/SignUp and call setActive without further navigation?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am a bit confused by the question, you can either have a custom flow, or mount SignIn/Up, right ? Can you give a n example when this is not the case ?

@LauraBeatris LauraBeatris Feb 7, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right, let me rephrase in another way then:

If I understood correctly, the modals get closed upon router navigation after setActive - but what happens if there's no navigation, you're just calling regular setActive - wouldn't we want to keep this current logic for closing SignIn / SignUp?

Also, setActive inner workings is still relately new to me as I'll be pushing some changes to it soon, so I'm mostly asking for my own understanding here 🫡

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. #resetComponentsState does not cover all modals which is weird on it's own.
  2. Having #resetComponentsState there, cause an open SignInModal to close if for whatever reason a setActive({session: null}) is called in a multi session app. Another weird side effect.

wouldn't we want to keep this current logic for closing SignIn / SignUp?
Our components will always redirect to afterSignIn or afterSignUp, which means we make a navigation outside the component so the modal will close.
The only modal component that exists today that does not navigate on setActive, is Reverification and it closes the modal manually (inside useAfterVerification).

Are we aligned that we care about closing the modal, only as long setActive is called within our components ? And as long as we always setActive({redirectUrl}) from within our component at the end of each flow the modals will close properly.

Removing #resetComponentsState might unblock afterAuth in a way, because now you can call setActive (without redirectUrl) from /sign-in/select-org/ and then internally navigate to /sign-in/subscribe and not having the modal close on you.

If you have scenarios that seem problematic with the changes that this PR proposes, please let us know as we might need to switch back to the more complex solution which allows for each component to close their own modal similarly to how we had setActive working prior to the deprecation of beforeEmit.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me! I'll make sure to consider that behavior when testing after-auth changes, and we also discuss further about that, thanks for handling those cases 🫡

@LauraBeatris LauraBeatris left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just missing the changeset description. Other than that, changes look good to me! 🫡

Comment thread packages/clerk-js/src/core/clerk.ts Outdated
expect(sessionCookieList.length).toBe(0);
});

test('closes the modal after delete', async ({ page, context }) => {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also add a test that covers the removed resetComponentState functionality? So closing a sign-in modal on sign in.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a bunch of tests in this commit

Comment thread packages/clerk-js/src/ui/lazyModules/providers.tsx Outdated
return () => {
unsubscribe();
};
// We are not expecting `onExternalNavigate` to change

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know we're not expecting it to change, but does providing it as a dependency break anything?

@panteliselef panteliselef Feb 10, 2025

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since we pass a non memoize function i think it will cause multiple subscriptions/unsubscribes

Comment thread packages/types/src/clerk.ts Outdated

testAgainstRunningApps({ withEnv: [appConfigs.envs.withEmailCodes] })('sign up flow @generic @nextjs', ({ app }) => {
test.describe.configure({ mode: 'serial' });
test.describe.configure({ mode: 'parallel' });

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to improve speed and does not cause tests to fail

Comment thread packages/types/src/clerk.ts Outdated
Co-authored-by: Dylan Staley <88163+dstaley@users.noreply.github.com>
@panteliselef

Copy link
Copy Markdown
Contributor Author

!snapshot

@clerk-cookie

Copy link
Copy Markdown
Collaborator

Hey @panteliselef - the snapshot version command generated the following package versions:

Package Version
@clerk/astro 2.2.0-snapshot.v20250212105537
@clerk/backend 1.24.1-snapshot.v20250212105537
@clerk/chrome-extension 2.2.9-snapshot.v20250212105537
@clerk/clerk-js 5.52.3-snapshot.v20250212105537
@clerk/elements 0.22.22-snapshot.v20250212105537
@clerk/clerk-expo 2.7.7-snapshot.v20250212105537
@clerk/expo-passkeys 0.1.20-snapshot.v20250212105537
@clerk/express 1.3.48-snapshot.v20250212105537
@clerk/fastify 2.1.21-snapshot.v20250212105537
@clerk/localizations 3.10.6-snapshot.v20250212105537
@clerk/nextjs 6.11.3-snapshot.v20250212105537
@clerk/nuxt 1.1.4-snapshot.v20250212105537
@clerk/clerk-react 5.22.13-snapshot.v20250212105537
@clerk/react-router 1.0.8-snapshot.v20250212105537
@clerk/remix 4.4.24-snapshot.v20250212105537
@clerk/shared 2.21.1-snapshot.v20250212105537
@clerk/tanstack-start 0.9.6-snapshot.v20250212105537
@clerk/testing 1.4.22-snapshot.v20250212105537
@clerk/themes 2.2.18-snapshot.v20250212105537
@clerk/types 4.46.0-snapshot.v20250212105537
@clerk/ui 0.3.23-snapshot.v20250212105537
@clerk/vue 1.1.12-snapshot.v20250212105537

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/astro

npm i @clerk/astro@2.2.0-snapshot.v20250212105537 --save-exact

@clerk/backend

npm i @clerk/backend@1.24.1-snapshot.v20250212105537 --save-exact

@clerk/chrome-extension

npm i @clerk/chrome-extension@2.2.9-snapshot.v20250212105537 --save-exact

@clerk/clerk-js

npm i @clerk/clerk-js@5.52.3-snapshot.v20250212105537 --save-exact

@clerk/elements

npm i @clerk/elements@0.22.22-snapshot.v20250212105537 --save-exact

@clerk/clerk-expo

npm i @clerk/clerk-expo@2.7.7-snapshot.v20250212105537 --save-exact

@clerk/expo-passkeys

npm i @clerk/expo-passkeys@0.1.20-snapshot.v20250212105537 --save-exact

@clerk/express

npm i @clerk/express@1.3.48-snapshot.v20250212105537 --save-exact

@clerk/fastify

npm i @clerk/fastify@2.1.21-snapshot.v20250212105537 --save-exact

@clerk/localizations

npm i @clerk/localizations@3.10.6-snapshot.v20250212105537 --save-exact

@clerk/nextjs

npm i @clerk/nextjs@6.11.3-snapshot.v20250212105537 --save-exact

@clerk/nuxt

npm i @clerk/nuxt@1.1.4-snapshot.v20250212105537 --save-exact

@clerk/clerk-react

npm i @clerk/clerk-react@5.22.13-snapshot.v20250212105537 --save-exact

@clerk/react-router

npm i @clerk/react-router@1.0.8-snapshot.v20250212105537 --save-exact

@clerk/remix

npm i @clerk/remix@4.4.24-snapshot.v20250212105537 --save-exact

@clerk/shared

npm i @clerk/shared@2.21.1-snapshot.v20250212105537 --save-exact

@clerk/tanstack-start

npm i @clerk/tanstack-start@0.9.6-snapshot.v20250212105537 --save-exact

@clerk/testing

npm i @clerk/testing@1.4.22-snapshot.v20250212105537 --save-exact

@clerk/themes

npm i @clerk/themes@2.2.18-snapshot.v20250212105537 --save-exact

@clerk/types

npm i @clerk/types@4.46.0-snapshot.v20250212105537 --save-exact

@clerk/ui

npm i @clerk/ui@0.3.23-snapshot.v20250212105537 --save-exact

@clerk/vue

npm i @clerk/vue@1.1.12-snapshot.v20250212105537 --save-exact

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants