Separation of concerns in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does Separation of concerns mean in React?

It means dividing a React app into parts where each part handles a specific job, like UI, data, or logic. This makes the app easier to understand and fix.

beginner

Why is separating UI and logic important in React components?

Separating UI and logic helps keep components simple and reusable. UI shows what users see, logic handles how data changes or actions happen.

intermediate

How do React hooks help with separation of concerns?

Hooks like useState and useEffect let you keep logic inside functions separate from UI code. You can reuse hooks to share logic across components.

intermediate

What is a common pattern to separate concerns in React apps?

Use container components for logic and data, and presentational components for UI. Containers fetch and manage data, presentational components just show it.

beginner

How does separation of concerns improve teamwork in React projects?

It lets team members work on different parts without conflicts. Designers can focus on UI components, developers on logic and data handling separately.

What is the main goal of separation of concerns in React?

A To avoid using hooks

B To write all code in one big component

C To combine UI and logic tightly

D To split code into parts that each handle a specific job

Separation of concerns means dividing code so each part has a clear job, making it easier to manage.

Which React feature helps keep logic separate from UI?

A useState and useEffect hooks

B Inline styles

C Class components only

D JSX comments

Hooks like useState and useEffect let you manage logic separately from UI rendering.

In the container-presentational pattern, what does the container component do?

A Runs tests

B Only shows UI

C Manages data and logic

D Handles CSS styling

Container components handle data fetching and logic, while presentational components focus on UI.

How does separation of concerns help when working in a team?

A Allows team members to work on different parts without conflicts

B Forces everyone to write the same code

C Makes code harder to read

D Prevents using components

Separating concerns lets team members focus on different areas, improving collaboration.

Which is NOT a benefit of separation of concerns in React?

A More reusable components

B More bugs due to mixed logic

C Easier to maintain and test code

D Clearer code structure

Separation of concerns reduces bugs by keeping code organized, not increasing them.

Explain how separation of concerns improves React component design.

Think about how splitting jobs in a team helps work go smoothly.

Describe the container and presentational component pattern and its role in separation of concerns.

Imagine one person cooks (logic) and another serves food (UI).

Practice

1. What does separation of concerns mean in React development?

easy

A. Dividing the app so each part handles one specific task

B. Writing all code in a single component for simplicity

C. Mixing UI and data logic in the same function

D. Using only class components instead of functions

Solution

1. Step 1: Understand the concept of separation of concerns

   It means each part of the app should focus on one clear responsibility, like UI or data handling.

2. Step 2: Identify the correct description

   Dividing the app so each part handles one specific task correctly describes dividing the app so each part handles one specific task, which matches the concept.

3. Final Answer:

   Dividing the app so each part handles one specific task -> Option A

4. Quick Check:

   Separation of concerns = dividing tasks clearly [OK]

Hint: Think: one part, one job in your app [OK]

Common Mistakes:

• Thinking all code should be in one component
• Mixing UI and logic in the same place
• Confusing separation with using classes

2. Which of the following is the correct way to separate UI and logic in React?

easy

A. Put all UI and logic inside one component's render method

B. Create a UI component and a separate hook for logic

C. Write logic inside HTML tags directly

D. Use inline styles to handle logic

Solution

1. Step 1: Identify proper separation of UI and logic

   React encourages using components for UI and hooks or functions for logic.

2. Step 2: Match options to this pattern

   Create a UI component and a separate hook for logic correctly separates UI in a component and logic in a hook, following best practices.

3. Final Answer:

   Create a UI component and a separate hook for logic -> Option B

4. Quick Check:

   UI + logic separated = Create a UI component and a separate hook for logic [OK]

Hint: Use hooks for logic, components for UI [OK]

Common Mistakes:

• Putting logic inside render method
• Trying to write logic inside HTML
• Using styles to control logic

3. Given this React code, what will be the output?

function UserName({ name }) {
  return <h1>User: {name}</h1>;
}

function UserLogic() {
  const user = { name: 'Anna' };
  return <UserName name={user.name} />;
}

medium

A. <h1>User: </h1>

B. Error: user is undefined

C. <h1>User: Anna</h1>

D. UserName component not found

Solution

1. Step 1: Trace the data flow from UserLogic to UserName

   UserLogic creates a user object with name 'Anna' and passes user.name as prop to UserName.

2. Step 2: Check UserName output

   UserName receives name='Anna' and renders <h1>User: Anna</h1> correctly.

3. Final Answer:

   <h1>User: Anna</h1> -> Option C

4. Quick Check:

   Prop passed correctly = <h1>User: Anna</h1> [OK]

Hint: Follow props from parent to child component [OK]

Common Mistakes:

• Assuming user is undefined outside UserLogic
• Expecting empty output if prop missing
• Confusing component names

4. What is wrong with this React code regarding separation of concerns?

function Profile() {
  const [user, setUser] = React.useState(null);
  React.useEffect(() => {
    fetch('/api/user')
      .then(res => res.json())
      .then(data => setUser(data));
  }, []);
  return <div>{user.name}</div>;
}

medium

A. Fetching data and UI rendering are mixed in one component

B. useEffect hook is used incorrectly

C. State should not be used in functional components

D. The fetch URL is invalid

Solution

1. Step 1: Identify concerns in the Profile component

   Profile handles both fetching user data and rendering UI, mixing logic and UI.

2. Step 2: Understand separation of concerns principle

   Best practice is to separate data fetching logic from UI components, e.g., using custom hooks.

3. Final Answer:

   Fetching data and UI rendering are mixed in one component -> Option A

4. Quick Check:

   Mixed logic and UI = Fetching data and UI rendering are mixed in one component [OK]

Hint: Keep data fetching separate from UI components [OK]

Common Mistakes:

• Thinking useEffect is wrong here
• Believing state can't be used in functions
• Assuming fetch URL is the problem

5. You want to improve this React app's separation of concerns:

function Dashboard() {
  const [data, setData] = React.useState(null);
  React.useEffect(() => {
    fetch('/api/data')
      .then(res => res.json())
      .then(json => setData(json));
  }, []);
  return <div>{data ? <Display data={data} /> : 'Loading...'}</div>;
}

Which change best improves separation of concerns?

hard

A. Remove useEffect and fetch data synchronously

B. Combine Display and Dashboard into one component

C. Fetch data inside Display component instead

D. Move data fetching into a custom hook and keep Dashboard for UI only

Solution

1. Step 1: Analyze current code responsibilities

   Dashboard handles both fetching data and rendering UI, mixing concerns.

2. Step 2: Choose best separation approach

   Moving data fetching to a custom hook isolates logic, leaving Dashboard focused on UI.

3. Final Answer:

   Move data fetching into a custom hook and keep Dashboard for UI only -> Option D

4. Quick Check:

   Separate logic in hooks, UI in components = Move data fetching into a custom hook and keep Dashboard for UI only [OK]

Hint: Use custom hooks for logic, components for display [OK]

Common Mistakes:

• Merging components reduces separation
• Fetching data inside UI components mixes concerns
• Removing useEffect breaks async data loading