Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
23 results across 1 active filter
Page 1 of 1
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Explains permission-aware navigation, guarded routes, server authorization, stale capabilities, and safe 401/403 handling.
Explains how to design DTOs, response shapes, UI needs, API compatibility, and frontend/backend ownership for a feature.
Explains how client-side validation, server-side validation, DTOs, domain rules, and user feedback work together.
Explains list/detail API boundaries, route state, prefetching, selected item behavior, and avoiding over-fetching.
Uses latest-request semantics, cancellation, identity checks, and explicit state transitions for changing inputs.
Uses HttpTestingController to verify request semantics and return controlled responses without calling a real server.
Places validation at the right form level and manages asynchronous checks without races or noisy requests.
Models pending, validation, success, retry, and authoritative server outcomes around a React 19 form Action.
Uses semantic forms, action state, pending feedback, server validation, focus behavior, and progressive enhancement.
Treats actions as public mutation endpoints with server validation, fresh authorization, idempotency, transactions, and safe errors.
Designs optimistic identity, pending state, reconciliation, rollback, and overlapping mutation behavior.
Explains upload UX, API boundaries, validation, progress, storage, scanning, failure handling, and safe download behavior.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Explains when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Uses functional interceptors for cross-cutting transport concerns without hiding domain behavior or unsafe retries.
Defines the serializable prop boundary, component composition pattern, and protections against leaking server-only data.
Covers Promise-based params and search parameters, async request APIs, generated route types, and runtime validation.
Uses runtime tokens for configuration and abstractions while distinguishing provider recipes and instance identity.
Chooses between blocking navigation for essential data and rendering a page-owned loading state.
Chooses between UI-coupled mutations and explicit HTTP contracts without treating either as a hidden trust boundary.
Layers optimistic routing checks with secure data-layer authorization across components, actions, and handlers.