programadorthi / kotlin-routing

An extensible and multiplatform routing system powered by Ktor

Hi there 👋

I'm Thiago Santos, an Android Developer since 2011 that likes to find patterns that should be improved and creating happyness to my workteam.

• 🇧🇷 I'm a Brazilian guy living on Aracaju/Sergipe;
• 👨‍💻 Working remote;
• 👨‍🎨 Daily trying improve projects architecture and build time;
• 🙅‍♂️ UI isn't my field. Yes, an Android dev that avoid touch UI code;
• 👷‍♂ Kotlin is now my primary language. Studying Rust in my free time to have a low level knowledge without touch C/C++;
• 🚧 My english need to be improved too because my communication skills are not so good;
• 🎮🐶 Classic games and my dogs are my free time tasks too.

Contact me @programadorthi

kotlin-routing's Issues

Update to Voyager rc06

Due to some changes in the Navigator function signature, the current version of kotlin-routing does not work with the latest version of Voyager. A simple update to the dependencies would allow kotlin-routing to be used with the latest Voyager.

WASM support

Kotlin routing is based on ktor.
The ktor main branch has support to WASM, but there is no release with it until now.
So next ktor release from main branch will bring support to kotlin routing too

Re-Add Voyager

Voyager now has API stability with the release of 1.0.0, now would be a great time to re-add it.

voyager implementation with path based navigation

Im setting up a compose multiplatform project using Voyager targeting web to start and im not seeing routes be appended to the URL when push()'ing them nor is the screen's defined by path/name navigatable via URL. Is there something i am missing in the config/setup or is my understanding of this incorrect?

val router = routing {
    screen("/home", name = TeaserScreen.key) {
        TeaserScreen
    }

    screen("/form", name = WaitlistFlow.key) {
        WaitlistFlow
    }
}

pushing is done via
LocalVoyagerRouting.current.pushNamed(TeaserScreen.key) or LocalVoyagerRouting.current.push(path ="/home")

I would expect localhost:8080/home to resolve while the server is running. (UI is updating appropriately just not browser paths).