Why Reusable components in React? - Purpose & Use Cases

The Big Idea

What if you could fix a bug once and see it fixed everywhere instantly?

The Scenario

Imagine building a website where you have to create the same button or card layout over and over again by copying and pasting code everywhere.

Every time you want to change the button color or text style, you have to find and update each copy manually.

The Problem

This manual approach is slow and risky because you might miss some copies or introduce mistakes.

It becomes a headache to keep your site consistent and up to date.

The Solution

Reusable components let you write the button or card code once and use it everywhere.

When you update the component, all places using it update automatically, saving time and avoiding errors.

Before vs After

✗ Before

const button1 = '<button style="color: red">Click</button>';
const button2 = '<button style="color: red">Submit</button>';

✓ After

function Button({ text }) {
  return <button style={{ color: 'red' }}>{text}</button>;
}

// Usage examples
<Button text="Click" />
<Button text="Submit" />

What It Enables

Reusable components make your code cleaner, easier to maintain, and faster to update across your whole app.

Real Life Example

Think of a shopping site where every product card looks the same. Using a reusable product card component means you only design it once, then show many products effortlessly.

Key Takeaways

Writing UI pieces once and reusing them saves time and effort.

Updating a component updates all its uses automatically.

Reusable components keep your app consistent and easier to manage.

Practice

1. What is the main benefit of using reusable components in React?

easy

A. They make your app run faster by default

B. They let you write less code and keep your app organized

C. They automatically fix bugs in your code

D. They prevent users from clicking buttons

Solution

1. Step 1: Understand the purpose of reusable components

   Reusable components are designed to be used multiple times to avoid repeating code.

2. Step 2: Identify the main benefit

   Using reusable components helps keep the app organized and reduces the amount of code you write.

3. Final Answer:

   They let you write less code and keep your app organized -> Option B

4. Quick Check:

   Reusable components = less code + organized app [OK]

Hint: Reusable means use again to save code and stay organized [OK]

Common Mistakes:

• Thinking reusable components speed up the app automatically
• Believing they fix bugs without coding
• Confusing reusable components with user interaction controls

2. Which of the following is the correct way to pass a prop named title with value "Hello" to a reusable component Card?

easy

A. <Card title=Hello />

B. <Card title={Hello} />

C. <Card "Hello"=title />

D. <Card title="Hello" />

Solution

1. Step 1: Recall JSX prop syntax

   Props are passed as attributes with name and value inside quotes or curly braces for expressions.

2. Step 2: Check each option

   <Card title="Hello" /> uses correct syntax: title="Hello". <Card title={Hello} /> misses quotes around string. <Card title=Hello /> lacks quotes or braces. <Card "Hello"=title /> has incorrect attribute format.

3. Final Answer:

   <Card title="Hello" /> -> Option D

4. Quick Check:

   Props need name="value" syntax [OK]

Hint: Props look like HTML attributes with quotes [OK]

Common Mistakes:

• Forgetting quotes around string prop values
• Using curly braces without variables
• Swapping prop name and value order

3. What will be the output of this React component usage?

function Greeting(props) {
  return <h1>Hello, {props.name}!</h1>;
}

<Greeting name="Alice" />
<Greeting name="Bob" />

medium

A. Hello, Alice!Hello, Bob!

B. Hello, Alice!

C. Hello, Bob!

D. Error: Cannot render two components like this

Solution

1. Step 1: Understand component usage

   Each <Greeting /> renders an <h1> with the passed name prop.

2. Step 2: Check the two usages

   First renders Hello, Alice!, second renders Hello, Bob!. Both outputs appear in order.

3. Final Answer:

   <h1>Hello, Alice!</h1><h1>Hello, Bob!</h1> -> Option A

4. Quick Check:

   Two components with different props render two greetings [OK]

Hint: Each component instance renders separately with its props [OK]

Common Mistakes:

• Thinking only one component renders
• Believing React errors on multiple components
• Confusing props with state causing wrong output

4. Identify the error in this reusable component code:

function Button(props) {
  return <button>Click {props.label}</button>
}

// Usage
<Button label=Submit />

medium

A. Button component must return a div, not button

B. Props cannot be used inside JSX

C. Missing quotes around the prop value in usage

D. Component name must start with lowercase

Solution

1. Step 1: Check prop usage syntax

   In JSX, string prop values must be in quotes or curly braces.

2. Step 2: Identify the error

   The usage <Button label=Submit /> lacks quotes around "Submit" causing syntax error.

3. Final Answer:

   Missing quotes around the prop value in usage -> Option C

4. Quick Check:

   String props need quotes [OK]

Hint: String props always need quotes in JSX [OK]

Common Mistakes:

• Thinking button must be wrapped in div
• Believing props can't be used inside JSX
• Using lowercase component names

5. You want to create a reusable List component that shows items with a custom renderItem prop function. Which approach correctly uses renderItem inside the component?

hard

A. function List(props) {
return <ul>{
props.items.map(item => <li>{props.renderItem(item)}</li>)
}</ul>;
}

B. function List(props) {
return <ul>{
props.items.map(props.renderItem(item))
}</ul>;
}

C. function List(props) {
return <ul>{
props.renderItem(props.items)
}</ul>;
}

D. function List(props) {
return <ul>{
props.items.forEach(item => props.renderItem(item))
}</ul>;
}

Solution

1. Step 1: Understand how to use renderItem with map

   To render a list, use map to transform each item into JSX, calling renderItem for each.

2. Step 2: Check each option

   function List(props) {
     return <ul>{
       props.items.map(item => <li>{props.renderItem(item)}</li>)
     }</ul>;
   }

   correctly maps items and calls renderItem inside <li>.

   function List(props) {
     return <ul>{
       props.items.map(props.renderItem(item))
     }</ul>;
   }

   calls renderItem incorrectly inside map.

   function List(props) {
     return <ul>{
       props.renderItem(props.items)
     }</ul>;
   }

   calls renderItem once with whole array.

   function List(props) {
     return <ul>{
       props.items.forEach(item => props.renderItem(item))
     }</ul>;
   }

   uses forEach which returns undefined, so no output.

3. Final Answer:

   Option A uses map and renderItem correctly inside list -> Option A

4. Quick Check:

   Use map with renderItem for lists [OK]

Hint: Use map with renderItem inside JSX to render lists [OK]

Common Mistakes:

• Using forEach instead of map for rendering
• Calling renderItem outside map or with wrong argument
• Passing whole array to renderItem instead of single item