A modern programming language that makes developers happier.

kotlinlang

Is it possible to use Locations with POST?

```
@Location("/v1/check") class IntegrationsContainer

...

post&lt;IntegrationsContainerC&gt; { body -&gt;
call.respond(realAppLogic(body))
}
```

but I get `2018-01-26 10:59:50.226 [nettyCallPool-4-1] ERROR Application - Unhandled: POST - /v1/check`

The properties in `IntegrationsContainerC` cannot be used for post variables

Well, you can still use locations but you just cannot route based on post body data

```@Location("/")
class Post(val test: Int) //only query params

data class Body(val x: Int) //actual body

post&lt;Post&gt; { post -&gt;// contains query params
    val body = call.receive&lt;Body&gt;() // contains body
    call.respond(body)
}
```

the unhandled POST probably means you did not specify all the query params in the `IntegrationsContainer` class

Ok - so the class uses in Location is just for (mandatory?) query params, and I need to use `call.receive&lt;T&gt;()` to get my actual class

but if my class (the `Body` class above) is a complex one, can it be used? If I get a JSON body with a `Content-Type: application/json` header, can I use something like Content-Negotiation feature, or should I just use a plain string / JSON serializer by hand?

You can have optional query params also. I think they just need a default value. ie `class Foo(val bar : String = "")`

content negotiation works with the exact same code

you just need to install one of the json features (gson, jackson) and it just works

```
fun Application.main() {
    install(DefaultHeaders)
    install(CallLogging)
    install(ContentNegotiation) {
        install(ContentNegotiation) {
            jackson {
                configure(SerializationFeature.INDENT_OUTPUT, true)
                registerModule(JavaTimeModule())
            }
        }
    }

    routing {
       post("/v1/check") {
            try {
                val myObj = call.receive&lt;MyObject&gt;()
                call.respond(HttpStatusCode.OK)
            } catch (e: Exception) {
                call.respond(HttpStatusCode.BadRequest)
            }
        }
    }
}
```

you have duplicate `install(ContentNegotiation)` calls, just a minor oversight