For API standpoint, `Locations` on big project inc...

# ktor

[neworldlt]

For API standpoint, Locations on big project increases messiness. It is a bit hard map API endpoints with logic calls because they both are in different code places. On another hand, I like them, because they map params with object. Do you consider to have something like that:

data class SearchRequest(q: String)

// a lot of code

route(“/api”) {
  get<SearchRequest>(“/search”) {
    //oneline call
  }
}