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
馃摎 What are you trying to do? Please describe.
I try get Promice in my page using useAsync or useFetch. When i use asyncData in client side - nuxt do default loding (progress line in top part), and after data will be loaded, nuxt do redirect in target page. When i use use useAsync or useFetch. nuxt make redirect in target page and affer start useAsync hook. How using useAsync give loading how
use asyncData ? Sorry for my English
When the page is loaded and a navigation happens with the normal asyncData nuxt will hold until the data is loaded. With the composition-API this can't be done with the current Nuxt APIs. I wrote useAsync with the intention to get as close as we can near the behavior of asyncData but when setup is called the navigation already happend.
With Nuxt 3 it is posible to do this but not with Nuxt 2 馃憥
With the composition-API this can't be done with the current Nuxt APIs.
Been having an issue in my SPA with this, been needing to handle the null refs before they resolve, and wondered why this didn't happen before. Is there anyway to possibly use the old asyncData alongside the composition API to get the blocking behaviour, or would I need to go back to using the regular options API in order to do so?
馃摎 What are you trying to do? Please describe.
I try get Promice in my page using useAsync or useFetch. When i use asyncData in client side - nuxt do default loding (progress line in top part), and after data will be loaded, nuxt do redirect in target page. When i use use useAsync or useFetch. nuxt make redirect in target page and affer start useAsync hook. How using useAsync give loading how
use asyncData ? Sorry for my English
馃攳 What have you tried?
鈩癸笍 Additional context
https://nuxtjs.org/docs/2.x/features/loading
The text was updated successfully, but these errors were encountered: