fix(clerk-js): Respect navigateAfterCreateOrganization in <OrganizationList/>#3209
Merged
panteliselef merged 4 commits intomainfrom Apr 17, 2024
Conversation
🦋 Changeset detectedLatest commit: 8d1fa5e The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 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 |
octoper
approved these changes
Apr 17, 2024
…ganizationurl-never-called
panteliselef
deleted the
elef/sdk-1632-organizationlist-aftercreateorganizationurl-never-called
branch
panteliselef
added a commit
that referenced
this pull request
Apr 18, 2024
9 tasks
panteliselef
added a commit
that referenced
this pull request
Apr 18, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
We were using the wrong callback by mistake, I've added a unit test that covers this case.
We will need to backport to v4, as the report came from there
Checklist
npm testruns as expected.npm run buildruns as expected.Type of change