new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

React Router · API · all subjects

error handling

2 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Error boundaries unified - no ErrorBoundary vs CatchBoundary distinction

React Router uses a single errorElement in the router for all errors. Both thrown errors and Response instances end up in the error boundary accessible via useRouteError(). Developers can maintain a similar split if needed by checking instanceof Response within the error handler.

useRouteError hook returns all error types

The useRouteError() hook returns any thrown value or Response instance. There is no distinction between error and catch boundaries, so both error types are handled through the same errorElement and accessible via useRouteError().

Give your agent this brain