Errors
Not found
Decide the 404 response with app.notFound, and hand over to it with c.notFound()
import { } from "@senrijs/senri";
const = ();
const = new <string, { : string }>();
.(() => `Not found: ${.}`);
.("/items/:id", ({ }, ) => {
const = .();
if (!) return .(); // hand over to the app.notFound handler
return ;
});- Requests that match no route go to the
app.notFoundhandler, or to the default 404 if there is none - When the route exists but the item does not,
c.notFound()hands over to the same place. Middleware can call it too
Write return c.notFound()
c.notFound() stops by throwing, so code after c.notFound(); does not run either way. Still write return: in a handler where c is not explicitly typed, TypeScript does not know that it stops here, and item stays possibly undefined.
Difference from HttpError(404)
It is almost the same as new HttpError(404), but it goes to app.notFound instead of onError.
await next()in outer middleware does not throw: it returns the 404 response. Checkres.status- A
try/catchin the same function catches it. Rethrow withif (err instanceof HttpError) throw err - Headers added with
c.header()(Set-Cookie, CORS and so on) are added to the 404 too - Called from an app mounted with
app.route(), the parent's handler is used - Called inside the
app.notFoundhandler, it gives the default 404. Called insideonError, it gives a fixed 500
The development 404 page shows "did you mean" only when no route matched.