You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've been debugging an application where the skip was not evaluated correctly and stumbled upon the issue of the queries being called randomly. I expected the queries to be called in the order in which I defined them, as its written in #430 too. In my project a lot of queries are dependent on values of other queries and if these are called before the other value, they will return wrong results as they use old values. I tried to debug this and initialized a minimal reproduction to find out how the order is defined: https://codesandbox.io/p/sandbox/nervous-voice-4kkyq8
Expected behavior
The order should be used to execute the queries. So in this example:
evaluate user skip()
call user query
evaluate post skip()
call post query
evaluate user skip()
call user query
evaluate post skip()
call post query
If this is not a bug a possibilty would be to add an (optional) order property to the queries, in which they should get executed:) Thank you for your help!
Describe the bug
I've been debugging an application where the skip was not evaluated correctly and stumbled upon the issue of the queries being called randomly. I expected the queries to be called in the order in which I defined them, as its written in #430 too. In my project a lot of queries are dependent on values of other queries and if these are called before the other value, they will return wrong results as they use old values. I tried to debug this and initialized a minimal reproduction to find out how the order is defined: https://codesandbox.io/p/sandbox/nervous-voice-4kkyq8
The current order is (most of the time):
Expected behavior
The order should be used to execute the queries. So in this example:
If this is not a bug a possibilty would be to add an (optional) order property to the queries, in which they should get executed:) Thank you for your help!
Versions
vue: 3.2.45 (Options API)
vue-apollo: 4.0.0
@apollo/client: 3.9.2
The text was updated successfully, but these errors were encountered: