Hi guys, I'm building a server side application. I would like to know what is the best practice to avoid having a big routing resource file ? How can we divide ? Imagine I have those urls for my API: GET /animal POST /animal GET /animal/:id POST /animal/:id and 20 URLs more starting by /animal.... I think having a "AnimalResource.kt" for all those url is not the best practice. How can I do ?

I found this article pretty helpful:

check out this sample too, it might give you some ideas: https://github.com/ktorio/ktor-samples/tree/a84eaadbe11c49bfe893f25b5a48278b477900fb/app/kweet/src

Myself I use extension functions on Routes to do the job.

install(Routing) {
        val konfig = HoconKonfigAdapter()
        val contextPath = konfig.get("ktor.deployment.context-path")
        route("$contextPath/api/v1") {
            val registry = feature(Metrics).registry

            healthEndPoints()
            metricsEndPoints(registry)
            routeWithMeasureTime {
                catalogSiEndPoints()
                reunionCatalogEditoEndPoints()
                telesurveillanceCatalogEditoEndPoints()
                catalogLegacyEndPoints()
            }
        }
    }

And the extension function looks like, each extension function in a separate kt file :

@KtorExperimentalLocationsAPI
fun Route.healthEndPoints() {
    get<HealthEndpoint> {
        call.respond(Health(HealthCheck.systemIs.state))
    }
}

Quite easy and simple.

a bit off topic, but when I try and use Locations like above, I get an error: