Rendering UI based on the props it receives, with little internal logic

Managing all of the application's global state directly

Configuring the app's routing for every page

A function that takes a component and returns a new, enhanced component

A component that can only render class components

It validates prop values at runtime and logs a console warning on mismatches

It transpiles props into plain HTML attributes

It enforces prop types at compile time like a static type checker

Prevents the event from bubbling up to parent element handlers

Cancels the browser's default action for that element

Removes the handler so it never fires again

A compile error, since keys must be strings

Any change to the input's value, such as each keystroke

Only when the surrounding form is submitted

The memoized value computed on a previous render

A freshly recomputed value, regardless of items

The URL pattern that must match for its element to render

The file location of the imported component

A re-render of the component with the updated state

It is a cleanup function React runs before the next effect or on unmount

It schedules the next effect to run immediately

Whenever userId changes to a new value on a re-render

On every single re-render, regardless of userId

By calling useContext with that same context object

By importing the Provider component's props directly

They keep the last value they ever received, forever

Forces a re-render without requiring a state change

A single React element, not wrapped in an array

Always a plain string of the child's text

The value attribute of the currently selected <option>

The index position of the option in the list

Checkboxes allow multiple selections, while radios in the same group allow only one

Radios allow multiple selections, while checkboxes allow only one

There is no functional difference between them in React

Its actual DOM position, since portals render outside the parent's DOM subtree

Its component tree position, since portals stay logically nested there

The reducer runs and returns a new state, causing a re-render

The action executes immediately as if it were a function call

The previous state is deleted permanently

The same memoized function reference from the previous render

A brand-new function reference every time

The return value of calling fn() immediately

React Quiz