I posted about this in the *Box Slack channel but didn't get any response - figured I'd log it here.
I'm seeing some unexpected behavior with the new Router, in particular, the toResponse() method. It seems (though I could be wrong), to be silently failing when an incorrect data type is passed in to the first argument.
That is, I was working with it and mistakenly passed in a struct, instead of a closure or rich HTML string:
In this case, a route was registered, but got handled by my default handler - the response was swallowed and lost, without an error.
It works correctly (as expected) when I pass in html:
I'd expect some type of error in the first case.