does anyone have any experience using the ktor loc...
# ktor
s
does anyone have any experience using the ktor locations api to get query parameters? I’m wondering if there’s a way to auto convert the casing strategy so the client can communicate in snake_case and the server can read the query params in as camelCase? Ktors Locations documentation offers no help, as it uses a simple case with one-word params that don’t need to define a casing strategy:
Copy code
GET parameters
If you provide additional class properties that are not part of the path of the @Location, those parameters will be obtained from the GET's query string or POST parameters:

@Location("/list/{name}")
data class Listing(val name: String, val page: Int, val count: Int)
Will match: /list/movies?page=10&count=20
Will construct: Listing(name = "movies", page = 10, count = 20)