fix(clerk-js): Ensure getToken() reads correct organization ID #4112
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
Fixes a bug where
getToken()
would read stale organization data fromclerk.organization
. This is problematic because in thesetActive()
flow we callgetToken()
beforeclerk.organization
is updated, and so we were reading a stale org ID when attempting to fetch a token for a new session.For impersonation specifically, this was problematic as the impersonator's session would be in memory while
setActive()
was being called with the impersonated session.Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change