Customize notFoundHandler

[yacinehmito]

In the process of migrating from Hono to Spiceflow, we found that there was no way of customizing notFoundHandler. When a route does not match, it always just outputs a 404 with a text body of "Not Found".

Hono provides the ability to customize this behavior through app.notFound(). Spiceflow does not provide such a method.

Would you be open to provide the ability to customize the notFoundHandler? If so, through which API?

Here are some options:

• Like Hono, through the addition of a handler that can be chained on (like the current onError).
• By providing in the context the information of which routes were matched. This would allow for a customization of the behavior by adding a last middleware, whose logic would roughly be "if there was no match, return whatever desired response and don't call next()".
• By passing the handler in the Spiceflow constructor.

Let me know what you think.

[mentatbot]

If you would like me to solve this issue, either tag me in a comment or check this box:

• Solve Issue

_{You can disable automatic comments on my settings page}

[yacinehmito]

For information, Elysia seems to rely on error handlers to achieve this: https://beta.elysiajs.com/life-cycle/on-error.html

[remorses]

I think adding a notFound method is the best solution

[yacinehmito]

Will open a PR today

[remorses]

Do you need this feature? Let's implement only features that are needed

[yacinehmito]

Yes I do. We are currently using it with Hono, because we want our 404 to return JSON, with information about the missing route.

[remorses]

Ok feel free to add a PR, subapps should inherit the root notFound handler