-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
fetchResults has no change on useQuery #1060
Closed
brunomperes opened this issue
Sep 24, 2020
· 2 comments
· Fixed by Shoutzor/frontend#141, Shoutzor/frontend#175, Shoutzor/frontend#179 or Shoutzor/frontend#181
Closed
fetchResults has no change on useQuery #1060
brunomperes opened this issue
Sep 24, 2020
· 2 comments
· Fixed by Shoutzor/frontend#141, Shoutzor/frontend#175, Shoutzor/frontend#179 or Shoutzor/frontend#181
Labels
Comments
This seems to be still an issue or it requires some documentation. |
any update here? |
This was referenced Aug 21, 2024
This was referenced Sep 11, 2024
This was referenced Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
On
v4
, passing the optionfetchResults: false
touseQuery
has no effect (and if it had any I'm not clear how it is different fromenabled: false
)To Reproduce
Steps to reproduce the behavior:
fetchResults: false
option to a component with composition APIExpected behavior
From what I see this option only exists in the v4 branch in a doc page and in a test.
So perhaps it's a leftover from v3 and it's just a matter of removing it.
If it is to be implemented though, ideally would be clear what is the difference between
fetchResults
andenabled
Versions
vue: 2.6.12
vue-apollo: v4.0.0-alpha.10
apollo-client: 3.1.2
Additional context
Link to docs page: https://v4.apollo.vuejs.org/api/use-query.html#parameters
The text was updated successfully, but these errors were encountered: