Loading
Pick a focused question that fits your time, stack, and interview goal.
12 results across 1 active filter
Page 1 of 1
Explains caching and revalidation choices for static, dynamic, user-specific, and frequently changing data.
Places state according to who owns it, how long it must live, and whether the URL or server is the source of truth.
Explains cleanup for subscriptions, timers, event listeners, and aborting stale fetches.
Explains loading, error, empty, success, refetch, stale data, and request lifecycle in client-rendered React.
Combines debounce cleanup, AbortController, and request identity to prevent stale search results.
Explains client cache keys, freshness, invalidation, refetching, optimistic updates, and server truth.
Applies an immediate reversible mutation, blocks overlapping writes, and restores the previous state on failure.
Explains when filters, sorting, pagination, and selection belong in search parameters and how to keep navigation predictable.
Uses discriminated unions to represent valid UI states and make transitions exhaustive.
Uses an explicit state model for initial loading, success, empty, recoverable error, and refetching.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
Explains route handlers as a frontend server boundary for cookies, API adaptation, auth, and backend calls.