CatchBoundary for expected errors in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a CatchBoundary component that receives caught errors.

Remix

export function CatchBoundary() {
  const caught = [1]();
  return <div>Caught status: {caught.status}</div>;
}

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

AuseRouteError

BuseLoaderData

CuseCatch

DuseActionData

Attempts:

3 left

💡 Hint

Common Mistakes

Using useLoaderData instead of useCatch.

Trying to access error data with useRouteError in CatchBoundary.

The useCatch hook is used inside CatchBoundary to access the caught response.

2fill in blank

medium

Complete the code to display the caught status code inside the CatchBoundary.

Remix

export function CatchBoundary() {
  const caught = useCatch();
  return <h1>Error [1]</h1>;
}

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

Acaught.status

Bcaught.message

Ccaught.error

Dcaught.data

Attempts:

3 left

💡 Hint

Common Mistakes

Using caught.message which is undefined.

Using caught.error which is not available in useCatch.

The caught.status contains the HTTP status code of the caught response.

3fill in blank

hard

Fix the error in the CatchBoundary to correctly render the caught status and message.

Remix

export function CatchBoundary() {
  const caught = useCatch();
  return (
    <div>
      <h2>Status: [1]</h2>
      <p>{caught.data.message}</p>
    </div>
  );
}

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

Acaught.status

Bcaught.statusCode

Ccaught.error.status

Dcaught.response.status

Attempts:

3 left

💡 Hint

Common Mistakes

Using caught.statusCode which does not exist.

Trying to access status inside caught.error or caught.response.

The correct property for the status code in the caught object is status.

4fill in blank

hard

Fill both blanks to render a friendly message for 404 and 401 errors inside CatchBoundary.

Remix

export function CatchBoundary() {
  const caught = useCatch();
  return (
    <div>
      {caught.status === [1] && <p>Page not found.</p>}
      {caught.status === [2] && <p>Unauthorized access.</p>}
    </div>
  );
}

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

A404

B401

C500

D403

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 401 and 403 status codes.

Using 500 which is a server error, not client error.

HTTP status 404 means 'Not Found' and 401 means 'Unauthorized'.

5fill in blank

hard

Fill all three blanks to create a CatchBoundary that shows status, statusText, and a retry button.

Remix

export function CatchBoundary() {
  const caught = useCatch();
  return (
    <main>
      <h1>Error [1]: [2]</h1>
      <button onClick={() => window.location.[3]()}>Try again</button>
    </main>
  );
}

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

Acaught.status

Bcaught.statusText

Creload

Dreplace

Attempts:

3 left

💡 Hint

Common Mistakes

Using window.location.replace() which navigates but does not reload.

Using caught.statusText in place of status.

The caught.status and caught.statusText show the error code and text. The reload method refreshes the page.

Practice

1. What is the main purpose of a CatchBoundary in Remix Framework?

easy

A. To display user-friendly messages for expected errors without crashing the app

B. To catch all unexpected errors and log them to the server

C. To replace the default error page with a blank screen

D. To automatically retry failed network requests

Solution

1. Step 1: Understand the role of CatchBoundary

   CatchBoundary is designed to handle expected errors gracefully by showing friendly messages to users.

2. Step 2: Differentiate from other error handling

   Unlike unexpected errors that crash the app, CatchBoundary prevents crashes by catching known error responses.

3. Final Answer:

   To display user-friendly messages for expected errors without crashing the app -> Option A

4. Quick Check:

   CatchBoundary = user-friendly error display [OK]

Hint: CatchBoundary shows expected errors nicely, not crashes [OK]

Common Mistakes:

• Confusing CatchBoundary with global error logging
• Thinking it handles unexpected crashes
• Assuming it retries failed requests

2. Which of the following is the correct way to access error details inside a CatchBoundary component?

easy

A. const caught = useCatch();

B. const error = useError();

C. const error = useBoundary();

D. const caught = useErrorBoundary();

Solution

1. Step 1: Recall the hook for CatchBoundary

   Remix provides useCatch() to get error details inside CatchBoundary.

2. Step 2: Verify other options

   Hooks like useError(), useBoundary(), or useErrorBoundary() do not exist in Remix for this purpose.

3. Final Answer:

   const caught = useCatch(); -> Option A

4. Quick Check:

   useCatch() = error details in CatchBoundary [OK]

Hint: Remember: useCatch() gets error info in CatchBoundary [OK]

Common Mistakes:

• Using non-existent hooks like useError()
• Confusing useCatch() with useErrorBoundary()
• Trying to access error from props instead of hook

3. Given this CatchBoundary code snippet, what will be rendered if the caught status is 404?

export function CatchBoundary() {
  const caught = useCatch();
  return (
    <div>
      <h1>Error {caught.status}</h1>
      <p>{caught.statusText}</p>
    </div>
  );
}

medium

A. Error 404Page Missing

B. Error 500Internal Server Error

C. Error 404Not Found

D. ErrorUnknown Error

Solution

1. Step 1: Identify caught status and statusText

   The caught object has status 404 and statusText 'Not Found' by default for 404 errors.

2. Step 2: Match rendered output

   The component renders <h1>Error 404</h1> and <p>Not Found</p> exactly as in

   Error 404

   Not Found

   .

3. Final Answer:

   <h1>Error 404</h1><p>Not Found</p> -> Option C

4. Quick Check:

   caught.status = 404, caught.statusText = Not Found [OK]

Hint: Caught status and statusText show error info [OK]

Common Mistakes:

• Assuming statusText is 'Page Missing' instead of 'Not Found'
• Mixing up 404 with 500 error messages
• Ignoring caught.status and using static text

4. What is wrong with this CatchBoundary component code?

export function CatchBoundary() {
  const caught = useCatch;
  return (
    <div>Error: {caught.status}</div>
  );
}

medium

A. useCatch should be imported from react, not remix

B. Caught object does not have a status property

C. CatchBoundary must return a fragment, not a div

D. useCatch is not called as a function

Solution

1. Step 1: Check how useCatch is used

   The code assigns const caught = useCatch; without parentheses, so useCatch is not called.

2. Step 2: Understand consequences

   Without calling useCatch(), caught is a function reference, not the error object, causing runtime errors when accessing caught.status.

3. Final Answer:

   useCatch is not called as a function -> Option D

4. Quick Check:

   useCatch() must be called to get error info [OK]

Hint: Always call useCatch() with parentheses [OK]

Common Mistakes:

• Forgetting parentheses on useCatch()
• Assuming caught is error object without calling hook
• Incorrect import source for useCatch

5. You want to show a custom message for 401 Unauthorized errors inside a CatchBoundary. Which code snippet correctly implements this behavior? A)

export function CatchBoundary() {
  const caught = useCatch();
  if (caught.status === 401) {
    return <div>Please log in to access this page.</div>;
  }
  return <div>Error {caught.status}</div>;
}

B)

export function CatchBoundary() {
  const caught = useCatch();
  if (caught.status === 403) {
    return <div>Please log in to access this page.</div>;
  }
  return <div>Error {caught.status}</div>;
}

C)

export function CatchBoundary() {
  const caught = useCatch();
  if (caught.status === 401) {
    return <div>Access denied.</div>;
  }
  return <div>Error {caught.status}</div>;
}

D)

export function CatchBoundary() {
  const caught = useCatch();
  if (caught.status === 401) {
    return <div>Error 401 occurred.</div>;
  }
  return <div>Please log in to access this page.</div>;
}

hard

A. Shows 'Please log in to access this page.' only for 403 errors, else generic error

B. Shows 'Please log in to access this page.' only for 401 errors, else generic error

C. Shows 'Access denied.' for 401 errors, else generic error

D. Shows 'Error 401 occurred.' for 401 errors, else 'Please log in to access this page.'

Solution

1. Step 1: Identify the correct status code and message

   401 means Unauthorized, so the message should prompt login only for status 401.

2. Step 2: Check the conditional logic and fallback

   Shows 'Please log in to access this page.' only for 401 errors, else generic error correctly checks for 401 and shows the login message only then, otherwise shows a generic error with status.

3. Final Answer:

   Shows 'Please log in to access this page.' only for 401 errors, else generic error -> Option B

4. Quick Check:

   401 status triggers login prompt in CatchBoundary [OK]

Hint: Match status code 401 exactly for login message [OK]

Common Mistakes:

• Using wrong status code like 403
• Showing login message for all errors
• Mixing messages between conditions