ribesg
10/11/2024, 9:34 AMfun Routing.setupSomeStuff() {
…
environment!!.monitor.subscribe(Routing.RoutingCallStarted) { call ->
…
call.route.parent?.toString()
…
}
…
}
RoutingCallStarted just disappeared and I can't find a context where call.route is a thing anymore. I don't see this breaking change documented anywhere.e5l
10/11/2024, 9:55 AMribesg
10/11/2024, 10:15 AMapplication.monitor.subscribe(RoutingRoot.RoutingCallStarted) { call ->
call.route.parent?.toString()
}
So Routing was renamed to RoutingRoot while a new different Routing was added? Or something?ribesg
10/11/2024, 10:16 AMRoutingCallStarted the IDE correctly suggests and imports RoutingRoot.RoutingCallStartedribesg
10/11/2024, 10:17 AMfun Routing.setupSomeStuff() to fun Route.setupSomeStuff(), the intention was for this function to be forced to be called at the root of the routing definition but it no longer seem to be an optionAleksei Tirman [JB]
10/14/2024, 9:22 AMI also had to changeYou can still usetofun Routing.setupSomeStuff(), the intention was for this function to be forced to be called at the root of the routing definition but it no longer seem to be an optionfun Route.setupSomeStuff()
Routing.setupSomeStuff .ribesg
10/14/2024, 9:25 AMrouting {} changedAleksei Tirman [JB]
10/14/2024, 9:26 AMfun main() {
embeddedServer(Netty, port = 8060, host = "0.0.0.0", module = {
routing {
setupSomeStuff()
}
}).start(wait = true)
}
fun Routing.setupSomeStuff() {
get {
call.respondText("GET")
}
}ribesg
10/14/2024, 9:27 AMAleksei Tirman [JB]
10/14/2024, 7:27 PMSoThewas renamed toRoutingwhile a new differentRoutingRootwas added? Or something?Routing
Routing is an interface and the RoutingRoot is a class that implements the interface.