Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow preventing `useFetch`/`useAsyncData` from firing immediately
See original GitHub issueEnvironment
n/a
Reproduction
n/a
Describe the bug
In my use case I’d find it particularily useful to prevent the useFetch/useAsyncData from firing immediately, as it has been implemented in the useFetch from VueUse:
https://vueuse.org/core/usefetch/#prevent-request-from-firing-immediately
… e.g. I’d still want to declare/prepare the call in the top level, but in scenarios when there is no logged in user and the request is only for the authorized ones, I can save the client from making an unnecessary request without having to wrap the call in a conditional statement.
Additional context
No response
Logs
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
More thinking, if purpose is really the refrashable behavior of asyncData having an option wouldn’t be a bad start at the end (otherwise we will end of with dosens of aliases).
I think this is quite an essential feature to have, because currently you can’t call data “on demand”.
For example: saving data when clicking a “save” button. You can’t actually do a post on demand currently with any of the composables.