🔗 Linked issue

resolves #18810

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

• This PR introduces a new status property in the object returned by the composables useAsyncData / useFetch and their lazy variations.
• This status property is a ref<string> that can contain the following values:
  • idle -> when request did not start
    • ({ immediate: false } and execute not called yet
    • { server: false } -> status should be idle on server side
  • pending -> when started
  • success -> when request succeeded
  • error -> when request failed
• It aims to bring a more powerful way to track the status of an async data request. Relying on pending flag only has a limitation detailed in this issue.
• Resolves status property for useAsyncData/useFetch ( lazy equivalents) #18810

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.