expo-data-fetching

原文涵盖的主题

• Expo Networking
• References
• When to Use
• Preferences
• Every Screen Has Four States
• Common Issues & Solutions
• 1. Basic Fetch Usage
• 2. React Query (TanStack Query)

You MUST use this skill for ANY networking work including API requests, data fetching, caching, or network debugging. Consult these resources as needed: Use this skill when: Implementing API requests Setting up data fetching (React Query, SWR) Using Expo Router data loaders (useLoaderData, web SDK 55+) Debugging network failures Implementing caching strategies Handling offline scenarios Authentication/token management Configuring API URLs and environment variables Avoid axios, prefer expo/fetch Design loading, error, empty, and content for screens that load data. These can overlap: a refresh error should coexist with cached content. Loading ≠ empty. Empty means resolved with zero items, not missing data. Handle initial loading, failure, and hydration before checking list length. In TanStack Query v5, isLoading means the first fetch is running; a disabled or offline-paused query can have no data without being loading. Show the prerequisite or offline state in that case. Empty is a designed state, not a blank list. Use ListEmptyComponent on FlatList/FlashList: explain why it is empty and offer the relevant next action. "No items yet" can offer Create; "No results" should offer changi

这里只展示节选，请以完整原文和当前要求为准。