-
Notifications
You must be signed in to change notification settings - Fork 53
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
EPIC: Version 2.0 #204
Comments
Stale issue message |
+1 for auth context API outside of react, primarily token information. |
I don't like that we sometimes have to recommend users to write stuff like So type LoginConfig = {
state?: string
additionalParameters?: TPrimitiveRecord
method?: 'redirect' | 'popup' | 'replaced-redirect'
}
function logIn (config?: LoginConfig) {} |
@dburles |
@soofstad I have data fetching logic that lives outside of React context which relies on the access token. Currently to get the token I am grabbing it directly from local storage, which works, but feels like a bit of a hack. |
A list of some things that can be done and included in a 2.0 release. Some are breaking, some are not. Most are up for discussion.
onRefreshTokenExpire()
handleRefreshError()
- maybe(?)useAuthContext()
- (?)logIn(undefine, undefine, True)
)The text was updated successfully, but these errors were encountered: