Error boundaries concept in React - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a class component that catches errors using an error boundary.

React

class ErrorBoundary extends React.Component {
  constructor(props) {
    super(props);
    this.state = { hasError: false };
  }

  static [1](error) {
    return { hasError: true };
  }

  render() {
    if (this.state.hasError) {
      return <h1>Something went wrong.</h1>;
    }
    return this.props.children;
  }
}

Drag options to blanks, or click blank then click option'

AcomponentDidCatch

BgetDerivedStateFromError

CrenderError

DhandleError

Attempts:

3 left

💡 Hint

Common Mistakes

Using componentDidCatch instead of getDerivedStateFromError here

Trying to use a non-existent lifecycle method

The getDerivedStateFromError method is a static lifecycle method used in error boundaries to update state when an error occurs.

2fill in blank

medium

Complete the code to log error details inside the error boundary.

React

class ErrorBoundary extends React.Component {
  componentDidCatch(error, info) {
    [1](error, info);
  }
  render() {
    return this.props.children;
  }
}

Drag options to blanks, or click blank then click option'

Athrow

Balert

Cconsole.error

Dconsole.log

Attempts:

3 left

💡 Hint

Common Mistakes

Using alert which interrupts user experience

Using throw which rethrows the error

console.error is used to log errors in the console, which helps in debugging.

3fill in blank

hard

Fix the error in the error boundary render method to properly display fallback UI.

React

render() {
  if (this.state.hasError) {
    return [1];
  }
  return this.props.children;
}

Drag options to blanks, or click blank then click option'

A<div>Error occurred</div>

BError occurred

C"Error occurred"

Dthis.props.children

Attempts:

3 left

💡 Hint

Common Mistakes

Returning a plain string instead of JSX

Returning this.props.children instead of fallback UI

The render method must return valid JSX. Returning a string alone is invalid; wrapping it in a <div> makes it valid JSX.

4fill in blank

hard

Fill both blanks to create an error boundary that updates state and logs errors.

React

class ErrorBoundary extends React.Component {
  static [1](error) {
    return { hasError: true };
  }

  [2](error, info) {
    console.error(error, info);
  }

  render() {
    if (this.state.hasError) {
      return <h2>Oops! Something went wrong.</h2>;
    }
    return this.props.children;
  }
}

Drag options to blanks, or click blank then click option'

AgetDerivedStateFromError

BcomponentWillUnmount

CcomponentDidCatch

DshouldComponentUpdate

Attempts:

3 left

💡 Hint

Common Mistakes

Using lifecycle methods unrelated to error handling

Mixing up method names

getDerivedStateFromError updates the state when an error occurs, and componentDidCatch logs the error details.

5fill in blank

hard

Fill the blanks to create a functional component that catches global errors using hooks.

React

import React, { useState, [1] } from 'react';

function ErrorBoundary({ children }) {
  const [hasError, setHasError] = useState(false);

  [2](() => {
    const handleError = () => setHasError(true);
    window.addEventListener('error', handleError);
    return () => window.removeEventListener('error', handleError);
  }, []);

  if (hasError) {
    return <h1>Something went wrong.</h1>;
  }

  return children;
}

export default ErrorBoundary;

Drag options to blanks, or click blank then click option'

AuseEffect

BuseCallback

CuseMemo

DuseRef

Attempts:

3 left

💡 Hint

Common Mistakes

Using useCallback or useMemo which are for memoization, not side effects

Forgetting to clean up event listeners

useEffect is used to run side effects like adding and cleaning up event listeners in functional components.

Practice

1. What is the main purpose of an Error Boundary in React?

easy

A. To catch JavaScript errors in child components and display a fallback UI

B. To manage state across multiple components

C. To optimize rendering performance

D. To handle user input validation

Solution

1. Step 1: Understand Error Boundary role

   Error boundaries catch errors in the components below them in the tree to prevent the whole app from crashing.

2. Step 2: Identify the correct purpose

   They show a fallback UI when an error happens, improving user experience.

3. Final Answer:

   To catch JavaScript errors in child components and display a fallback UI -> Option A

4. Quick Check:

   Error boundaries catch errors = C [OK]

Hint: Error boundaries catch errors and show fallback UI [OK]

Common Mistakes:

• Confusing error boundaries with state management
• Thinking error boundaries optimize rendering
• Assuming error boundaries handle input validation

2. Which of the following is the correct way to define an Error Boundary component in React?

easy

A. A class component implementing componentDidCatch and getDerivedStateFromError

B. A functional component using useErrorBoundary hook

C. A class component implementing componentDidMount and shouldComponentUpdate

D. A functional component with useEffect to catch errors

Solution

1. Step 1: Recall Error Boundary requirements

   Error boundaries must be class components that implement componentDidCatch and getDerivedStateFromError lifecycle methods.

2. Step 2: Identify correct lifecycle methods

   Only A class component implementing componentDidCatch and getDerivedStateFromError lists these two required methods correctly.

3. Final Answer:

   A class component implementing componentDidCatch and getDerivedStateFromError -> Option A

4. Quick Check:

   Class + componentDidCatch + getDerivedStateFromError = A [OK]

Hint: Error boundaries are class components with special lifecycle methods [OK]

Common Mistakes:

• Thinking functional components can be error boundaries
• Confusing lifecycle methods needed for error boundaries
• Using hooks that don't exist for error boundaries

3. Given this Error Boundary class component, what will be rendered if ChildComponent throws an error?

class ErrorBoundary extends React.Component {
  constructor(props) {
    super(props);
    this.state = { hasError: false };
  }
  static getDerivedStateFromError(error) {
    return { hasError: true };
  }
  componentDidCatch(error, info) {
    console.log('Error logged:', error);
  }
  render() {
    if (this.state.hasError) {
      return <h1>Something went wrong.</h1>;
    }
    return this.props.children;
  }
}

// Usage:
// <ErrorBoundary><ChildComponent /></ErrorBoundary>

medium

A. The original ChildComponent UI is shown

B. The app crashes with an uncaught error

C. Nothing is rendered (blank screen)

D. An error message Something went wrong. is shown

Solution

1. Step 1: Understand error handling in ErrorBoundary

   If ChildComponent throws an error, getDerivedStateFromError sets hasError to true.

2. Step 2: Check render output when error occurs

   When hasError is true, the component renders the fallback UI: <h1>Something went wrong.</h1>.

3. Final Answer:

   An error message Something went wrong. is shown -> Option D

4. Quick Check:

   Error caught shows fallback UI = D [OK]

Hint: Error sets state to show fallback UI, not original child [OK]

Common Mistakes:

• Expecting child UI to show despite error
• Thinking error causes app crash
• Assuming blank screen on error

4. What is wrong with this Error Boundary component code?

class MyErrorBoundary extends React.Component {
  constructor(props) {
    super(props);
    this.state = { error: null };
  }
  componentDidCatch(error, info) {
    this.setState({ error });
  }
  render() {
    if (this.state.error) {
      return <h2>Error occurred</h2>;
    }
    return this.props.children;
  }
}

medium

A. componentDidCatch should not call setState

B. It lacks the static method getDerivedStateFromError to update state on error

C. The constructor should not initialize state

D. render method must not return children

Solution

1. Step 1: Check error state update method

   Error boundaries must implement getDerivedStateFromError to update state when an error happens.

2. Step 2: Identify missing static method

   This code only uses componentDidCatch to set state, which is incorrect because componentDidCatch is for side effects, not state updates.

3. Final Answer:

   It lacks the static method getDerivedStateFromError to update state on error -> Option B

4. Quick Check:

   Missing getDerivedStateFromError static method = A [OK]

Hint: State update on error must be in getDerivedStateFromError [OK]

Common Mistakes:

• Updating state inside componentDidCatch
• Forgetting static getDerivedStateFromError
• Misusing lifecycle methods for error handling

5. You want to create an Error Boundary that logs errors to an external service and shows a fallback UI. Which of the following is the best approach?

class LoggingErrorBoundary extends React.Component {
  constructor(props) {
    super(props);
    this.state = { hasError: false };
  }
  static getDerivedStateFromError(error) {
    return { hasError: true };
  }
  componentDidCatch(error, info) {
    // ???
  }
  render() {
    if (this.state.hasError) {
      return <div><h1>Oops!</h1><p>Try refreshing.</p></div>;
    }
    return this.props.children;
  }
}

What should replace // ??? to correctly log errors without causing issues?

hard

A. Call an async logging function directly without try/catch

B. Update state again inside componentDidCatch to trigger re-render

C. Use a try/catch inside componentDidCatch to call the logging service safely

D. Ignore logging and only show fallback UI

Solution

1. Step 1: Understand componentDidCatch role

   componentDidCatch is for side effects like logging errors but should handle errors safely to avoid crashing.

2. Step 2: Choose safe logging approach

   Using try/catch inside componentDidCatch when calling async logging prevents unhandled errors from breaking the app.

3. Final Answer:

   Use a try/catch inside componentDidCatch to call the logging service safely -> Option C

4. Quick Check:

   Safe error logging with try/catch in componentDidCatch = B [OK]

Hint: Wrap logging calls in try/catch inside componentDidCatch [OK]

Common Mistakes:

• Calling async logging without error handling
• Updating state inside componentDidCatch causing loops
• Skipping logging and losing error info