Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(table): use status instead of deprecated pending in useFetch and useAsyncData #2084

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

samuelbelo
Copy link
Contributor

πŸ”— Linked issue

No issue linked.

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ 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 pull request change the 'pending' property of AsyncData and Fetch calls in favor of the 'status' property.
The 'pending' prop is deprecated and will likely be removed in future versions, according to the documentation.

πŸ“ Checklist

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

@benjamincanac benjamincanac changed the title docs(Table): change deprecated pending prop to status on fetch and asyncData calls docs(table): use status instead of deprecated pending in useFetch and useAsyncData Sep 3, 2024
@benjamincanac benjamincanac merged commit 0527f8d into nuxt:dev Sep 3, 2024
1 check passed
@benjamincanac
Copy link
Member

Thanks! 😊

binhtranhuu pushed a commit to binhtranhuu/nuxt-ui that referenced this pull request Sep 14, 2024
patrick-hofmann pushed a commit to patrick-hofmann/nuxt-ui that referenced this pull request Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants