Why is there no routing support for handling websocket requests with sink and source?

The routing directives only support handling websocket requests with a Flow[Message, Message, Any].

Because nobody contributed it yet ;)

Makes sense ;-)

There are Flow.fromSinkAndSource and Flow.fromSinkAndSourceCoupled which you can use for these situations when you want to handle them separately. It also makes you immediately think about “should termination of either side also terminate the other, or not?” which is a very tricky aspect of websockets people are often not aware off until it behaves not like they assumed. So the hope was here that that guides a bit into thinking about it more.