-
Notifications
You must be signed in to change notification settings - Fork 49
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
feat!: implement rfc#136 (oauth, token refresh) #142
Conversation
If you call login/logout with an expired token set, it will throw a 401.
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.
Thank you, just a few changes. And where is the Breaking Change? I can't see the commit?
The breaking change was "Modification to auto-fetch may change intended behaviour" I wasn't sure how the initial one worked, as it only seemed to fetch when the plugin was registered? |
Also moved the check into a composable, so it can be used elsewhere.
Thanks for this PR, I will release this changes when we documented it and fixed other bugs. |
This PR is now released, but we have to document this changes. |
I will do it if for you is ok |
Sure, you can make an own branch and a PR for that. |
Types of changes
Modification to auto-fetch may change intended behaviour
Description
Resolves:
#136
#131
Checklist: