Question - what do you think about the naming for ...

# ktor

[hhariri]

Question - what do you think about the naming for strongly-typed routes, i.e. Locations?

1. Find it straightforward and understand what it means
2. I find it confusing with HTTP Location header
3. Other (please use thread)

[hhariri]

Other thoughts…

[Hamza]

I know the concept is extremely powerful, but I found it confusing to understand while reading the documentation and never got around to using it. Maybe that's just me though, as I know people who use them, and love them

[andylamax]

Funny, I read about them, I understood them, but never go to use them. To me it felt like too much effort for just a simple thing

[Matteo Mirk]

I found it confusing since day 1. Just from the name
1. I couldn’t imagine it was a feature related to routing
2. I thought it had to do with HTTP Location header
Why not just rename it to something closer to its intended usage, such as @Route , @Path or a more RESTful @Resource ?

[Casey Brooks]

I like the idea of strongly-typed routes, but don’t care for the syntax (and the name is also not very descriptive). Using a bunch of annotations to make a route type-safe seems very un-idiomatic for Ktor, and it pulls the routing info (path) away from the routing { } block.

I would prefer to simply add a type parameter to a normal route, rather than moving the path info into an annotation. And if this were supported, it seems like it should be part of the core routing feature, not in a separate artifact.

routing {
    // original route
    get("/list/{name}") {
        call.respondText("Listing ${listing.name}, page ${listing.page}")
    }

    // with static type (all that's changed is the addition of the type parameter)
    get<Listing>("/list/{name}") { listing ->
        call.respondText("Listing ${listing.name}, page ${listing.page}")
    }
}

[rharter]

I’ve actually been working on some similar things in this space, and realized as I did that Location is a bit misleading since it is really describing a type-safe Request. For instance, I’ve been working on some type-safe template support (using freemarker), and the idea of having a type-safe Response gets a bit conflated with the type-safe. The name Location sort of hijacks the entire space while only actually serving half of the endpoint location.