We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@web3-react v6 @uauth/js v2.4.0
Login Integration TLDR: username is set a an optional value but breaks when not set and attempting to get UserInfo
await activate(uauth); do the redirect, approve and sign via metamask user is redirected to correct authorize route in this route we run uauth.user()
await activate(uauth);
uauth.user()
uauth/packages/js/src/Client.ts
Line 422 in 52618c8
to then call authorization()
authorization()
Line 416 in 52618c8
Here we see that the interface AuthorizationOptions username as optional
AuthorizationOptions
uauth/packages/js/src/types.ts
Line 155 in 52618c8
but here we see that username is verified as a required field using the _getUsername to verify one exist.
username
_getUsername
uauth/packages/js/src/ClientStore.ts
Line 134 in 52618c8
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@web3-react v6
@uauth/js v2.4.0
Login Integration
TLDR: username is set a an optional value but breaks when not set and attempting to get UserInfo
await activate(uauth);
do the redirect, approve and sign via metamask
user is redirected to correct authorize route
in this route we run
uauth.user()
uauth/packages/js/src/Client.ts
Line 422 in 52618c8
to then call
authorization()
uauth/packages/js/src/Client.ts
Line 416 in 52618c8
Here we see that the interface
AuthorizationOptions
username as optionaluauth/packages/js/src/types.ts
Line 155 in 52618c8
but here we see that
username
is verified as a required field using the_getUsername
to verify one exist.uauth/packages/js/src/ClientStore.ts
Line 134 in 52618c8
The text was updated successfully, but these errors were encountered: