Just wonder will Jetpack Compose and Jetbrains Compose be merged onto one "Compose library" eventual...

# compose

[Tlaster]

Just wonder will Jetpack Compose and Jetbrains Compose be merged onto one "Compose library" eventually? Because it's a little bit confusing when writing a Compose library, I'll have to write 2 separate modules cause there're Jetbrain Compose and Jetpack Compose but the source code is basically the same. Or maybe there's a better way I haven't found out yet?

[Filip Wiesner]

There was a thread in #compose-desktop about this:
https://kotlinlang.slack.com/archives/C01D6HTPATV/p1616329156094100

[Tlaster]

Thanks! Good to hear that!

[CLOVIS]

Not 100% sure I understand your issue, but I've got Multiplattorm compose working with no code duplication: https://gitlab.com/braindot/clovis/-/tree/master/compose

[CLOVIS]

(if you want to replicate this, you will need the root settings.gradle.kts, and possibly a few things from the root build.gradle.kts as well—there is a minimal example in the JetBrains repo that could be easier to adapt)