Hook naming conventions in React - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why must React hooks start with 'use'?

React hooks must start with the word use. Why is this naming rule important?

A React uses the 'use' prefix to identify hooks and enforce rules about their usage.

B The 'use' prefix is required to make hooks compatible with older React versions.

C Hooks must start with 'use' to make them asynchronous functions.

D It is a stylistic choice with no effect on how React works.

💡 Hint

Think about how React detects hooks inside components.

React relies on the 'use' prefix to identify hooks so it can apply rules like calling them only at the top level and inside React functions. This helps React manage state and effects correctly.

📝 Syntax

intermediate

Which hook name is valid according to React conventions?

Choose the valid React hook name from the options below.

A dataUseFetch

B fetchDataHook

C hookUseData

D useDataFetch

💡 Hint

Remember hooks must start with 'use'.

Only names starting with 'use' are recognized as hooks by React. 'useDataFetch' follows this rule.

❓ component_behavior

advanced

What happens if a custom hook does NOT start with 'use'?

Consider a custom hook named fetchData (without 'use' prefix). What is the likely behavior when used inside a React component?

A React will treat it as a hook anyway because it is called inside a component.

B React will not recognize it as a hook and may break the rules of hooks, causing bugs or warnings.

C The hook will run twice on every render.

D React will throw a syntax error during compilation.

💡 Hint

Think about how React enforces hook rules.

React identifies hooks by their 'use' prefix. Without it, React cannot enforce rules like calling hooks only at the top level, which can cause bugs or warnings.

🔧 Debug

advanced

Identify the naming error causing a React warning

Given this custom hook code, which naming mistake causes React to warn about invalid hook usage?

function fetchUserData() {
  const [user, setUser] = React.useState(null);
  // ...fetch logic
  return user;
}

A The hook must return an array, not a single value.

B The hook should be declared inside the component, not outside.

C The function name should start with 'use' like 'useFetchUserData'.

D React hooks cannot use useState inside custom hooks.

💡 Hint

Check the function name against React hook naming rules.

React expects custom hooks to start with 'use' to identify them properly. Naming it 'fetchUserData' breaks this rule and causes warnings.

❓ state_output

expert

What is the output of this React component using a custom hook with incorrect naming?

Consider this React component and custom hook:

function fetchCount() {
  const [count, setCount] = React.useState(0);
  React.useEffect(() => {
    const timer = setInterval(() => setCount(c => c + 1), 1000);
    return () => clearInterval(timer);
  }, []);
  return count;
}

function Counter() {
  const count = fetchCount();
  return 
{count}
;
}

What will happen when <Counter /> is rendered?

A React will render the count but show a warning about invalid hook call due to naming.

B React will render the count and update it every second without warnings.

C React will throw a runtime error because hooks cannot be called inside functions without 'use' prefix.

D React will render '0' once and never update the count.

💡 Hint

Consider React's hook rules and naming conventions.

The hook works but React warns because the function name does not start with 'use'. This breaks the hook naming convention and React's hook rules.