Why custom hooks are used in React - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Custom Hooks in React

Why do developers create custom hooks in React?

A To directly manipulate the DOM elements

B To replace all class components with functional components

C To reuse stateful logic across multiple components easily

D To increase the size of the application bundle

💡 Hint

Think about how to avoid repeating the same code in different parts of your app.

Custom hooks let you share logic that uses React state and effects between components without repeating code.

❓ component_behavior

intermediate

Behavior of a Custom Hook

Consider a custom hook that fetches data and returns loading status and data. What is the main benefit of using this hook in multiple components?

A Each component can share the same fetching logic without rewriting it

B It forces all components to fetch data at the same time

C It disables React's built-in hooks like useState

D It automatically caches data in the browser storage

💡 Hint

Think about how to avoid copying the same code for fetching data in every component.

Custom hooks encapsulate logic like data fetching so multiple components can use it without duplicating code.

📝 Syntax

advanced

Correct Syntax for a Custom Hook

Which option shows the correct way to define a custom hook that returns a count and a function to increment it?

React

function useCounter() {
  const [count, setCount] = React.useState(0);
  const increment = () => setCount(count + 1);
  return { count, increment };
}

A function useCounter() { let count = 0; function increment() { count++; } return { count, increment }; }

B function counterHook() { const [count, setCount] = React.useState(0); const increment = () => setCount(count + 1); return [count, increment]; }

C function UseCounter() { const count = 0; function increment() { count++; } return { count, increment }; }

D function useCounter() { const [count, setCount] = React.useState(0); const increment = () => setCount(count + 1); return { count, increment }; }

💡 Hint

Custom hooks must start with 'use' and use React hooks inside.

Option D correctly defines a custom hook using React's useState and returns an object with count and increment function.

🔧 Debug

advanced

Identifying Error in Custom Hook Usage

What error will occur if a custom hook is called inside a regular JavaScript function instead of a React component or another hook?

A React Hook "useCustomHook" cannot be called inside a regular function

B TypeError: useCustomHook is not a function

C SyntaxError: Unexpected token 'useCustomHook'

D No error, it works fine

💡 Hint

React hooks have rules about where they can be called.

React enforces that hooks can only be called inside React function components or other hooks. Calling them elsewhere causes an error.

❓ state_output

expert

State Behavior in Custom Hook Across Components

Given a custom hook that uses useState internally, what happens to the state when two different components use this hook?

A Both components share the same state instance from the hook

B Each component has its own independent state from the hook

C The state resets to initial value whenever a component re-renders

D The hook state is global and updates all components simultaneously

💡 Hint

Think about how React hooks work inside components.

Each call to a custom hook creates a separate state instance for that component. States are not shared unless explicitly designed.

Practice

1. Why do React developers create custom hooks?

easy

A. To reuse stateful logic across multiple components

B. To style components with CSS

C. To replace React components entirely

D. To write HTML inside JavaScript

Solution

1. Step 1: Understand the purpose of hooks

   Hooks in React let you use state and other React features without writing a class.

2. Step 2: Identify why custom hooks are made

   Custom hooks let you reuse stateful logic easily across different components, avoiding repetition.

3. Final Answer:

   To reuse stateful logic across multiple components -> Option A

4. Quick Check:

   Custom hooks = reuse logic [OK]

Hint: Custom hooks reuse logic, not styles or HTML [OK]

Common Mistakes:

• Thinking custom hooks are for styling
• Believing custom hooks replace components
• Confusing hooks with HTML syntax

2. Which of the following is the correct way to name a custom hook in React?

easy

A. useFetchData

B. fetchDataHook

C. FetchData

D. hookUseFetch

Solution

1. Step 1: Recall React naming conventions for hooks

   React requires custom hooks to start with the word 'use' to identify them as hooks.

2. Step 2: Check each option

   Only 'useFetchData' starts with 'use', following React's convention.

3. Final Answer:

   useFetchData -> Option A

4. Quick Check:

   Custom hook names start with 'use' [OK]

Hint: Custom hooks always start with 'use' [OK]

Common Mistakes:

• Not starting the name with 'use'
• Using camel case without 'use' prefix
• Confusing component names with hook names

3. What will be the output of this React component using a custom hook?

function useCounter() {
  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 = useCounter();
  return 
{count}
;
}

medium

A. Throws an error because hooks can't be used here

B. Always shows 0 and never changes

C. A number that increases by 1 every second starting from 0

D. Shows a static string 'count'

Solution

1. Step 1: Analyze the custom hook useCounter

   It initializes count to 0 and sets up a timer to increase count by 1 every second.

2. Step 2: Understand the component output

   The Counter component uses useCounter and displays the count, which updates every second.

3. Final Answer:

   A number that increases by 1 every second starting from 0 -> Option C

4. Quick Check:

   useCounter returns incrementing count [OK]

Hint: Custom hooks can return changing state values [OK]

Common Mistakes:

• Thinking count stays 0 forever
• Believing hooks can't be used in functions
• Assuming output is a string, not a number

4. Identify the error in this custom hook usage:

function useData() {
  const [data, setData] = React.useState(null);
  fetch('https://api.example.com/data')
    .then(res => res.json())
    .then(json => setData(json));
  return data;
}

function App() {
  const data = useData();
  return <div>{JSON.stringify(data)}</div>;
}

medium

A. Custom hooks cannot return data

B. The fetch call should be inside useEffect to avoid infinite loops

C. useState is used incorrectly and should be replaced with useRef

D. The component should not call the custom hook

Solution

1. Step 1: Check where fetch is called in useData

   fetch is called directly inside the hook body, causing it to run on every render, leading to infinite loops.

2. Step 2: Correct usage with useEffect

   fetch should be inside a useEffect with an empty dependency array to run only once on mount.

3. Final Answer:

   The fetch call should be inside useEffect to avoid infinite loops -> Option B

4. Quick Check:

   Side effects go inside useEffect [OK]

Hint: Put side effects like fetch inside useEffect [OK]

Common Mistakes:

• Calling fetch directly in hook body
• Misusing useState instead of useEffect
• Thinking hooks can't return values

5. You want to share logic for fetching user data and managing loading state across several components. Which approach best uses custom hooks to solve this?

hard

A. Store user data in a global variable outside React

B. Write the fetch logic separately in each component to avoid dependencies

C. Use a class component instead of hooks for shared logic

D. Create a custom hook that fetches user data and returns both data and loading state

Solution

1. Step 1: Understand the need for reusable logic

   Fetching data and managing loading state is stateful logic that can be reused with a custom hook.

2. Step 2: Evaluate options for sharing logic

   Creating a custom hook that returns data and loading state allows multiple components to share this logic cleanly.

3. Final Answer:

   Create a custom hook that fetches user data and returns both data and loading state -> Option D

4. Quick Check:

   Custom hooks share stateful logic best [OK]

Hint: Custom hooks bundle related state and logic for reuse [OK]

Common Mistakes:

• Duplicating fetch code in every component
• Using class components instead of hooks
• Using global variables that break React's state flow