mirror of
https://github.com/nuxt/nuxt.git
synced 2024-11-24 06:35:10 +00:00
48 lines
1.2 KiB
Markdown
48 lines
1.2 KiB
Markdown
---
|
|
description: This wrapper around useFetch triggers navigation immediately.
|
|
---
|
|
|
|
# `useLazyFetch`
|
|
|
|
`useLazyFetch` provides a wrapper around `useFetch` that triggers navigation before the handler is resolved by setting the `lazy` option to `true`.
|
|
|
|
## Description
|
|
|
|
By default, [useFetch](/docs/api/composables/use-fetch) blocks navigation until its async handler is resolved.
|
|
|
|
> `useLazyFetch` has the same signature as `useFetch`.
|
|
|
|
:ReadMore{link="/docs/api/composables/use-fetch"}
|
|
|
|
## Example
|
|
|
|
```vue
|
|
<template>
|
|
<div v-if="pending">
|
|
Loading ...
|
|
</div>
|
|
<div v-else>
|
|
<div v-for="post in posts">
|
|
<!-- do something -->
|
|
</div>
|
|
</div>
|
|
</template>
|
|
|
|
<script setup>
|
|
/* Navigation will occur before fetching is complete.
|
|
Handle pending and error states directly within your component's template
|
|
*/
|
|
const { pending, data: posts } = useLazyFetch('/api/posts')
|
|
watch(posts, (newPosts) => {
|
|
// Because posts starts out null, you won't have access
|
|
// to its contents immediately, but you can watch it.
|
|
})
|
|
</script>
|
|
```
|
|
|
|
::alert{type=warning}
|
|
`useLazyFetch` is a reserved function name transformed by the compiler, so you should not name your own function `useLazyFetch`.
|
|
::
|
|
|
|
:ReadMore{link="/docs/getting-started/data-fetching#uselazyfetch"}
|