Hey I have a question about

UUID

usage in ROOM database with the new built in adapter. We decided to move from

Long

@PrimaryKey

type to

UUID

because of integrity reasons. Now we need to migrate those ids. So when writing a migration we use raw SQL where we lose the ability to use built in converters (AFAIU at least) so we can’t insert it as

String

or something else (cant use the `UUIDUtil`from ROOM too). What would be the suggested way to migrate

Long

ids to

UUID

to use the build in adapter? Maybe someone else encountered a similar issue?

When applying Kotlinx-Serialization and KMP-NativeCoroutines plugins in the same KMP module, getting this error during configuration:

> Cannot add task 'commonizeNativeDistribution' as a task with that name already exists.

Any ideas?

is it possible to use ROOM in compose desktop applications?

is there a way to AOT kotlin jvm apps

KMM - Monorepo or Multirepo? Hi all. In the last weeks as we’ve been setting up our KMM project, we came across interesting debate about which repo approach should we use - mono repo or multi repo. What are you guys using in your KMM projects? Are there any issues you’ve faced that made you switch repo from mono to multi or vice versa? Both of these approaches have its own pros and cons, but I see more pros in using multi repo approach (shared logic added as a git submodule into ios/android repo): • smaller repo size (specially in the future there may be platform specific binaries in the repo, same goes for assets…) • platform specific CI settings, versioning (tags), pull requests and branches • no need to clone whole project, specially as there are some guys on android and some guys working on iOS project • in the future there might be other platforms using shared module and having all platforms in one repo does not make sense IMO. • and so on One challenge is, how to assure “green-develop/master” on shared module. We’ve been thinking about approach where some feature will be implemented, and there will be changes on common repo. We could probably open a pull request and once tests and everything is green, git workflow could open PR’s for iOS and Android as well. Any opinions, feedback how you guys face this? What are best practices for huge projects?

I sometimes find myself doing

AnimatedVisibility(visible = someState != null) {
    MyUi(someState!!)
}

should compose/kotlin be able to figure out that I don't need !! or, am I setting up a potential footgun for myself here?

Also, how to remove toolbar from Preview?

I checked sonarqube has support for detekt (I want to totally remove the sonar original issues and use detekt reports, or in other words, I want a GUI to see detekt issues + codecoverage via sonarqube. https://docs.sonarqube.org/latest/analysis/external-issues/ In another hand, I have seen there is a sonar-detekt plugin. With the official property is not enough so I need to use this plugin? What are the differences?

Any ideas how to get `Cell`s have the same height in

LazyVerticalGrid

?

What's the conventional wisdom on mockito-kotlin vs MockK? I feel like mockito-kotlin is more intuitive