yep - so in the spike (which isn't actually where ...
# http4k
d
yep - so in the spike (which isn't actually where I thought it was - sorry about that ­čÖé ), you'd do quite a similar thing to what you'd do with the contract-style routing, but slightly rejigged so that everything is built using a completely typesafe DSL thing. One of the problems is that Kotlin lacks an HList, so building endpoints with completely arbitrary number of inputs is pretty tricky. the fact that data classes aren't real tuples also doesn't help.