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
Describe the bug Calling $auth.login() returns a promise that will resolve right after login, but before the call (and the result) of fetchData.
$auth.login()
fetchData
To Reproduce
await Vue.$auth.login(…)
Vue.$auth.user()
https://codepen.io/glandos/pen/YzQNjeB?editors=1112 You can see that loginNotOK follow the pattern of the current code, while loginOK returns the result of the promise.then call.
loginNotOK
loginOK
promise.then
Expected behavior login returned promise should resolve when all information are there. Especially, this code should be valid:
login
await Vue.$auth.login({username, password}) assert Vue.$auth.user() !== null
This is not the case today.
Is this a wanted behavior? Should I opened a PR to fix that?
The text was updated successfully, but these errors were encountered:
d0whc3r
No branches or pull requests
Describe the bug
Calling
$auth.login()
returns a promise that will resolve right after login, but before the call (and the result) offetchData
.To Reproduce
await Vue.$auth.login(…)
Vue.$auth.user()
right afterhttps://codepen.io/glandos/pen/YzQNjeB?editors=1112
You can see that
loginNotOK
follow the pattern of the current code, whileloginOK
returns the result of thepromise.then
call.Expected behavior
login
returned promise should resolve when all information are there. Especially, this code should be valid:This is not the case today.
Is this a wanted behavior? Should I opened a PR to fix that?
The text was updated successfully, but these errors were encountered: