-
Notifications
You must be signed in to change notification settings - Fork 46
feat: Fetch credentials on token expiry/401 #604
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
Conversation
…edentials, invalidateCredentials.
…ab's remote connector about invalidation.
🦋 Changeset detectedLatest commit: 413ad7d The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 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 |
I have had the dev release of this work tested by @Omnicpie. Feedback was positive. |
…th older services.
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.
Looks good to me
Improved credentials management and error handling. Credentials are invalidated when they expire or become invalid based on responses from the PowerSync service. The frequency of credential fetching has been reduced as a result of this work.
For web we need to communicate over the comlink from the worker to the main tab that invalidation needs to happen.
Follows a similar pattern applied to PowerSync Dart.
Alternative approach to #528