Skip to content

Conversation

@andrew-propelauth
Copy link
Contributor

Currently, you have to specify an authUrl and we construct the client. This is fine, and still supported, but we do have cases where people want to use the client outside of a react context and it's nicer to just let them pass in a client to share.

Additionally, this fixes a case where unmounting and remounting the authprovider can create extra clients.

Currently, you have to specify an authUrl and we construct the client.
This is fine, and still supported, but we do have cases where people
want to use the client outside of a react context and it's nicer
to just let them pass in a client to share.

Additionally, this fixes a case where unmounting and remounting the authprovider
can create extra clients.
Copy link
Contributor

@pfvatterott pfvatterott left a comment

Choose a reason for hiding this comment

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

Tested. LGTM!

@andrew-propelauth andrew-propelauth merged commit 0fb65d0 into main Dec 2, 2025
1 of 2 checks passed
@andrew-propelauth andrew-propelauth deleted the can-specify-client branch December 2, 2025 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants