You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that the (err, req, res, next) signature is not supported, however,
that feature is really missing.
For example, my app have three separate routers with totally different behaviors:
generates html pages
the api
static files
and each router needs to deal with errors very differently.
The text was updated successfully, but these errors were encountered:
Hello, as you may have read from previous issues and documentation, the hyper-express middleware system at the moment is very different from Express.js in both its operation and internal logic.
Middlewares and Routes are different without sharing the same signature.
Middlewares execute in a hierarchical manner where order is GLOBAL -> LOCAL -> ROUTE_SPECIFIC
Unfortunately, we only support a global error handler at the moment. I do think that a router specific error handler should be possible in theory since it would be an additive change rather than a breaking one.
Do you have reference on the signature, behavior and expectation of this feature?
I understand that the (err, req, res, next) signature is not supported, however,
that feature is really missing.
For example, my app have three separate routers with totally different behaviors:
and each router needs to deal with errors very differently.
The text was updated successfully, but these errors were encountered: