-
Notifications
You must be signed in to change notification settings - Fork 253
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
fix(remix): Deprecate loadUser
, loadSession
and loadOrganization
on rootAuthLoader
#3443
Conversation
🦋 Changeset detectedLatest commit: 150f20f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
🪛 I think it would be better to mark them as deprecated for now and drop them in the next major release of the SDK |
…ootAuthLoader options
69d05fc
to
d48eb37
Compare
loadUser
, loadSession
and loadOrganization
from rootAuthLoaderloadUser
, loadSession
and loadOrganization
on rootAuthLoader
@octoper Agreed! Just pushed! |
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.
🔥
@panteliselef Yes, we should have removed them. |
Co-authored-by: George Desipris <73396808+desiprisg@users.noreply.github.com>
I think we should also use the |
Currently,
rootAuthLoader
types suggest the usage ofloadUser
,loadSession
andloadOrganization
boolean options. Using any of these will result to a call to Clerk Backend API on each root loader execution. This results in rate limiting issues for apps with many users and affects scalability.This PR deprecates these 3 options so that they're not misused.
Relevant issue: #1043
Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change