-
Notifications
You must be signed in to change notification settings - Fork 25
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
Not reactive #21
Comments
As a workaround you could do a manual redirect in the callback function of the login. Like so:
|
@Pok09
As described here |
Hey there! Currently, I'm in the process of a big rewrite that will automatically update the authentication status after a user logs in or logs out. This means there will be some breaking changes, so I want to make sure I take my time to document everything properly. |
Thanks for this plugin
I noticed that the data is not reactive, you have to reload the page for the changed state
const {user, loggedIn} = useAuth()
Example if all the pages have the same header, after connection the connection button must disappear after changing state (loggedin), but nothing
you have to reload the page
The text was updated successfully, but these errors were encountered: