Which statement describes the typical pattern for creating a custom hook?

Which statement describes the typical pattern for creating a custom hook?

• A. It begins with 'hook' and cannot call other hooks.
• B. It begins with 'use', calls other hooks, and returns state or utilities.
• C. It must be a class-based function.
• D. It should not return anything.

Answer: (B)

A custom hook follows a simple pattern: it’s a function whose name starts with use, it can call other hooks inside, and it returns something that components can use. Starting with use signals to React and your tooling that this is a hook and should follow the rules of hooks. Inside the function, you typically call other hooks like useState, useEffect, useContext, or useMemo to assemble the behavior you want. At the end, you return the state value, a setter, or an object of utilities that encapsulate the logic so components can reuse it easily. This combination—use-prefix, internal hook calls, and returning actionable values—is what makes the pattern standard and practical for sharing stateful logic. The other statements don’t fit because a hook isn’t named with hook, it isn’t limited to not calling other hooks, and a hook isn’t restricted to void return; its purpose is to expose state or actions for components to consume.

A custom hook follows a simple pattern: it’s a function whose name starts with use, it can call other hooks inside, and it returns something that components can use. Starting with use signals to React and your tooling that this is a hook and should follow the rules of hooks. Inside the function, you typically call other hooks like useState, useEffect, useContext, or useMemo to assemble the behavior you want. At the end, you return the state value, a setter, or an object of utilities that encapsulate the logic so components can reuse it easily. This combination—use-prefix, internal hook calls, and returning actionable values—is what makes the pattern standard and practical for sharing stateful logic. The other statements don’t fit because a hook isn’t named with hook, it isn’t limited to not calling other hooks, and a hook isn’t restricted to void return; its purpose is to expose state or actions for components to consume.