Hi, please is there a way to automatically generate swagger ui in ktor?

I want to collect

navController.currentBackStackEntryFlow

and must to do it in CoroutineScope. I have few questions 1. Where can I read about relation of coroutines and composables 2. Where better to collect this flow? Looks like there are mechanisms in compose to handle coroutines, but i am not sure that good practice to do as i did. 3. Even if it is good practice - what is better to use as key for

LaunchedEffect

? I select activity, but it seems meaningless

What's the difference between Box and Surface components? The Surface looks like a Material Theme specific component and that's it?

can takeif be used instead of a normal if else in the following code somehow?

Is there a way to enforce indent tabs instead of spaces? EDIT --- So far my research on the matter shows that there is no way to use tabs with either detekt or ktlint. I get the desire to avoid indent-wars, but this effectively prevents teams with existing code bases and style guides based on tabs to use either detekt or ktlint, or forces them to disable all the relevant rule(set)s and write their own. Plainly that sucks 😞

I have one really strange issue with Dokka

java.lang.UnsupportedOperationException: PermittedSubclasses requires ASM9

I found one related error in Kotlin, which is already fixed. I have Dokka 1.9.20, Kotlin 1.9.24, Gradle 8.8, AGP 8.5.1. I tried to run

./gradlew  buildEnvironment

to see build script dependencies and there is only

org.ow2.asm:asm:9.6

, so I don't understand why it should write that it requires ASM9, when there is ASM 9 already.

Hi, when I try to bump kotlin version from

1.9.21

to

1.9.23

or

2.0.0

in a KMM project I am getting errors. For

1.9.23

the error is

org.gradle.api.InvalidUserCodeException: Build was configured to prefer settings repositories over project repositories but repository 'ivy' was added by build file 'app/build.gradle.kts'
	...

and for `2.0.0`:

* What went wrong:
java.lang.ExceptionInInitializerError (no error message)
> org.jetbrains.kotlin.konan.target.KonanTarget$IOS_ARM32

The gradle plugin version is

8.3.1

. What can be the reason? 🧵

Hi, I have a question about implementing Kotlin suspend functions in Swift with an Kotlin interface. AFAIK, suspend functions are translated as functions with completion handler in the generated ObjC header. In Swift, you then have the option of implementing the functions either with a completion handler or as an async/await function. If I’m using async/await as follows, is it safe? Does the @MainActor annotation work correctly? Is cancellation supported?

// Kotlin
interface LoginProvider {
    suspend fun login()
}

// Kotlin
class AndroidLoginProvider: LoginProvider {
    override suspend fun login() { }
}

// Swift
class IOSLoginProvider: LoginProvider {
    @MainActor
    func login() async { }
}


// Kotlin
class AuthenticationRepository {
    [...]

    fun login() = withContext(Dispatchers.IO) {
        loginProvider.login()
    }
}

In the KMP documentation, I only find a clear indication that async/await usage is experimental when suspend functions are called from swift (see https://kotlinlang.org/docs/native-objc-interop.html#suspending-functions). However, this is not the case when a suspend function is implemented via an interface. Also this article https://www.jetbrains.com/help/kotlin-multiplatform-dev/multiplatform-connect-to-apis.html describes only how to implement such apis in the iOS source set in shared. If anyone can provide me with further information or sources, I would be very grateful. Thank you :)

applicationId vs namespace. Google recommends to have these 2 with the same value. Although KMP by default creates app id as

com.myapplication.appId

and name space for shared module as`com.myapplication.appid.android/common`. Is there are any particular reason why? To prevent possible collisions if you have lots of code in both app and shared modules? Currently it adds headache for me because my Firebase setup is in the shared module, as well as the google-json file, which is created for the

com.myapplication.appId

and of course fails to build for the

com.myapplication.appid.android/common

kotlinx.datetime

provides a default serializer for

kotlinx.datetime.LocalDateTime

which can only parse an ISO string like

"2023-02-20T22:07:12.668"

. Unfortunately, JavaScript/TypeScript's

Date().toISOString()

produces a string like

"2023-02-20T22:07:12.668Z"

- with the extra Z at the end. Do I need to change all my

LocalDateTime

to

Instant

? Or write my own serializer? Seems a little bit of unnecessary work 😞 Or should I just hack it and chop off the 'Z' before posting my Json from the front end?