Multiple `useLazyAsyncData` within a composable becomes non lazy
good first issuebug馃敤 p3-minor
# Multiple `useLazyAsyncData` within a composable becomes non lazy
`useAsyncData` is not blocking the client navigation
3.xworkaround availablepending triage
useAsyncData doesn't block navigation with lazy: false
3.xpending triage
Remove `pending` in favor of `status` in data fetching composables
good first issue馃嵃 p2-nice-to-have鈿狅笍 breaking change4.x5.x
Accessing async data cache object with a new composable
3.xpending triage