I want a route like

/status/{id}

so you can do GET /status/abc-123 ...looking at https://www.http4k.org/cookbook/nestable_routes/ I have:

"/status/{id}" meta {
   summary = "get the status"
} bindContract GET to handler

When I

curl <http://localhost:800/status/123>

I get a 404. If i change the route to just be :

"/status" meta {
  summary = "get the status"
} bindContract GET to handler

I get a 200 Ok if I

curl <http://localhost:8000/status>

What am I missing?

I do get a 200 if I do

curl "<http://localhost:8000/status/\{id\}>"

@Codecraig you can't mix the contract and non-contract forms. You need to define a path lens instead to capture your parameter

"/status" / Path.of("id)

...

or if you're using a routes block then your original version should work for capturing the path param from the request

I have this..

contract(OpenApi(ApiInfo(...), "/docs/swagger.json", myRoute())

fun myRoute = "/status/{id}" meta { ... } bindContract GET to handler

Yeah - you need to use a Path lens

so right now, myRoute returns a ContractRoute...if I change it to

fun myRoute = "/status/" / Path.of("id") meta { ... } bindContract GET to handler

It not longer returns a ContractRoute which is needed by the

contract(OpenApi(...))

portion

Changing to a Path lens results in a return type of

Pair<RouteBinder(String) -> HttpHandler>, Status>

Your bind now takes a function and not a handler

you change has now fallen back to the stanrdard Kotlin Pair

to()

you need something like

... to { id -> { Response(OK).bodyString(id.toString()) }

Ah ok, thank you for the help

Np 😀

The latest version of http4k-contract has broken some existing code - it looks like we were directly setting the body field of RouteMetaDsl, which is now internal. Am I right in thinking those calls should be changed to call

receiving

?

@darrenhobbs yeppity. That body parameter was causing confusion/inconsistency. If you look at the release notes, you can see it was released in v3.103.0

I was looking at the "Dynamic path test" https://www.http4k.org/guide/testing/ and was wondering how to get a "route" to invoke with a

Request

, when my current setup has `ContractRoute`'s

@Codecraig you need to convert your contract to a router - you can do this through wrapping it in a contract block, or use

route.toRouter(Root)

. We could probably make that betterer tbh..

I have a

ContractRoute

which doesn't have a

toRouter

, what is

route

in this case?

Ah maybe that's internal.. let me check

Oh yea, I see it is internal.

@Codecraig you can just do this then:

contract(route)

and that should give you a handler you can call

yup, that worked. thanks again for the help

With a ContractRoute, is it possible to customize the response given to clients if they submit a request not matching what I expect? For example, if the contract says the request must be JSON and have a field

name

and

value

and a client submits an empty body...I'd like to provide a standard "error" response to them, however, my handler doesn't get invoked for me to do that (b/c the framework sees the body isn't what i expect)

@Codecraig you could do it by writing a customised lens

map()

chain - so

Body.json().map { try to unmarshall here, and catch and rethrow the Exception }.toLens()

thanks

How would I go about hosting the swagger UI with http4k?

is there docs somewhere for setting that up? or is that a "swagger" thing?