Repository navigation
fix(mosaic): stop the trigger badge flickering with an inline renderTriggerBadge #10456
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@clerk/mosaic': patch | ||
| --- | ||
|
|
||
| Fix the `UserButton` and `OrganizationSwitcher` trigger badge flickering when the popup opens with an inline `renderTriggerBadge` function. The badge is now only requested again when the displayed user, organization or session changes, and each request uses the latest `renderTriggerBadge` you pass. |
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
Script executed:
Repository: clerk/javascript
Length of output: 10201
Settle the org_9 badge result before asserting that the badge is hidden.
toHaveBeenCalledWithpasses once the renderer runs, which happens before its promise settles. While the request is pending,useSwitcherTriggerControllerreturnsbadge: undefined. The followingnot.toHaveTextContent('Pro plan')therefore passes before thenullresult is applied, so it does not check the settled outcome. A regression that shows a badge after anullor rejected result may not fail here. The same pattern appears in thenulltest inorganization-switcher.feature.test.tsxand in the rejection case ofhides the badge for false or on failurein this file.Resolve the org_9 result inside
actand assert after it settles:🧪 Suggested test change
it('hides the badge while pending and for null without changing the name', async () => { const badge = deferred<{ id: string; label: string } | null>(); + const nextBadge = deferred<{ id: string; label: string } | null>(); const renderTriggerBadge = vi.fn(({ id }: { id: string }) => - id === 'org_1' ? badge.promise : Promise.resolve(null), + id === 'org_1' ? badge.promise : nextBadge.promise, ); @@ await act(() => clerk.setActive({ organization: 'org_9' })); await waitFor(() => expect(renderTriggerBadge).toHaveBeenCalledWith({ kind: 'organization', id: 'org_9' })); + await act(() => nextBadge.resolve(null)); expect(trigger()).not.toHaveTextContent('Pro plan');