Pick a focused question that fits your time, stack, and interview goal.
15 results across 1 active filter
Page 1 of 1
Implements labeled fields, client validation, error summaries, focus recovery, and pending submission state.
Builds a route-level Next.js failure UI with safe reporting, retry, and an escape route while keeping expected errors out of the boundary.
Models file validation, progress, cancellation, failure, and retry without losing the selected file.
Combines debounce cleanup, AbortController, and request identity to prevent stale search results.
Moves non-deterministic browser-only rendering behind a stable server snapshot and post-hydration update.
Applies an immediate reversible mutation, blocks overlapping writes, and restores the previous state on failure.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.
Guards a mutation immediately, exposes pending state, and restores the command after failure.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
Uses server-resolved capabilities for presentation while keeping the mutation endpoint authoritative.
Uses an explicit state model for initial loading, success, empty, recoverable error, and refetching.
Keeps data and secrets on the server while sending a small serializable model to an interactive client component.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
Tests validation, focus, pending state, and the save contract through accessible user interactions rather than component internals.
Tests one browser-to-database practice workflow with isolated fixtures, resilient locators, durable assertions, and reliable cleanup.