We're making good progress on the http4k integrati...
# kotless
d
We're making good progress on the http4k integration but have got a couple of questions: 1. We're writing the Http4kParser but have no idea about how to go about testing that it works - the PSI API is a bit involved. Is there an easy way to set it up to help us pass in the Kotless subclass and see how the ProcessorContext is populated? 2. One of the things that http4k currently supports for all of the 6 serverless platforms (Lambda/GCF, OpenWhisk/IBM, Tencent, Alibaba & Azure) is that you can deploy entire applications with many dynamic routes. This effectively means that you configure the APIGateway in proxy mode with a wildcard route. It doesn't look like that is currently possible with Kotless using the URIPath class, but might be fairly simple to add with a bit of remodelling (maybe using a sealed class to represent Proxy/URIPath options). Is this something that's been considered?