Closed jakaplan closed 2 years ago
@amomchilov I'd appreciate getting your thoughts on this approach. If you think it's a good idea, I'd also welcome a code review although this approach is currently incomplete - it should also have applicable decoding/encoding errors go to the route's error handler and not the global one.
@amomchilov Thought on this approach? Genuinely unsure if this is actually helpful or not.
Not convinced this is the correct approach, so closing for the time being. Can always be reconsidered in the future.
Sorry, this slipped through the cracks, I never even took a look at it :o
A global error handler remains, but now exists for global errors like a request for route that's not registered or insecure connection.
Decoding of a message type and encoding of a reply type and/or error type are still sent to the global error handler. Ideally those would also be sent to the route specific one. If we like this approach, can take a look at doing that next.