Tag view

#react

Cross-subject tag search for related interview cards.

Clear

Results update as you type. Press / to jump straight into search.

Tagged with react

57 cards

React Medium Theory

Accessibility in React: semantic HTML, keyboard support, ARIA, forms, and modal accessibility

Accessibility in React still starts with semantic HTML, keyboard support, clear form behavior, and careful ARIA usage.

  • React does not replace accessibility fundamentals
  • Use semantic elements first
  • Buttons, forms, and modals need keyboard-friendly behavior

Accessibility in React: semantic HTML, keyboard support, ARIA, forms, and modal accessibility

React Medium Theory

Common React interview comparisons

React interviews often rely on contrast questions such as props vs state, state vs ref, useEffect vs useLayoutEffect, and Context vs Redux.

  • Comparisons reveal trade-offs
  • Many pairs differ by ownership, timing, or performance
  • Use cases matter more than memorized slogans

Common React interview comparisons

React Medium Theory

Common React pitfalls

Many React bugs come from mutable state, wrong keys, bad effect dependencies, overused context, and mixing too much logic into UI components.

  • Do not mutate state directly
  • Missing dependencies cause subtle bugs
  • Too much state or context makes components harder to reason about

Common React pitfalls

React Medium Theory

Component communication, sibling communication, and composition vs inheritance in React

Data usually flows down from parent to child, while child-to-parent and sibling communication happen through callbacks, lifted state, or shared providers.

  • Parent-to-child uses props
  • Child-to-parent uses callback props
  • Composition is preferred over inheritance in React

Component communication, sibling communication, and composition vs inheritance in React

React Medium Theory

Context performance, Context vs Redux, and when global state is really needed

Context is not a full performance or tooling replacement for every state management problem, and global state should be introduced only when local state is no longer enough.

  • Not all shared data needs Redux
  • Context updates can fan out widely
  • Global state should solve a real coordination problem

Context performance, Context vs Redux, and when global state is really needed

React Hard Theory

Data fetching in React: useEffect, loading and error states, cleanup, race conditions, AbortController, React Query, SWR, and server vs client state

React data fetching is about both getting data and managing cache, loading, error, cancellation, and freshness correctly.

  • Server state behaves differently from local UI state
  • Race conditions happen when requests overlap
  • Libraries like TanStack Query and SWR help with caching and synchronization

Data fetching in React: useEffect, loading and error states, cleanup, race conditions, AbortController, React Query, SWR, and server vs client state