-
Notifications
You must be signed in to change notification settings - Fork 66
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
$asyncComputed state #75
Comments
Hey, I've added a test case that tries to test this issue, but I'm not managing to reproduce it. Can you take a look, and help me track down what's causing your issue? |
Hm. I can add I'm using |
Neither of those should matter (especially since the default Can you give me a code excerpt that seems to trigger this behaviour for you? |
If the |
I see what you're saying, and I've tried to replicate exactly that in the test suite here: vue-async-computed/test/index.js Lines 1017 to 1050 in 3be0d85
The test still passes just fine, so I doubt that the problem is in something the test covers here. Is it possible that something else is going on here? Perhaps a reactivity issue of some sort in your code? (Along the lines of #18?) If you can make an example (e.g. in codepen.io) that shows this issue happening, I'll look into it further. |
$requestState.state is always
updating
if computed resolves to0
. It is never becomessuccess
.The text was updated successfully, but these errors were encountered: