A modern programming language that makes developers happier.

kotlinlang

Screenshot 2023-11-08 at 12.07.27 PM.png

Hey, having all of these source sets is great, but in Compose we are using desktopMain as well, I think it would be nice to have it as well when we add jvm("desktop") target.

The problem is that `"desktop"` in that case is a dynamic name for a JVM target, you could call it anything, and these source set accessors are static, pre-defined properties (<https://github.com/JetBrains/kotlin/blob/master/libraries/tools/kotlin-gradle-plugin/src/common/kotlin/org/jetbrains/kotlin/gradle/dsl/KotlinMultiplatformSourceSetConventions.kt|implemented here>).

So you can either get the source set the regular way
```sourceSets {
    val desktopMain by getting
    desktopMain.dependencies {
        implementation(compose.desktop.currentOs)
    }
}```
Or if you _really_ want an accessor that has autocompletion and is the same as the others, you can define one yourself
```// Somewhere in scope, like top level in the Gradle build file
val NamedDomainObjectContainer&lt;KotlinSourceSet&gt;.desktopMain by KotlinSourceSetConvention

// In the kotlin{} block
sourceSets {
    desktopMain.dependencies {
        implementation(compose.desktop.currentOs)
    }
}```

On a related topic, if you name a target's source set like `jvm("desktop")`, does it still get connected into the default hierarchy template the same as if it had the default `jvm` source set name?

image.png

Well, the `jvm` target in the default hierarchy really just depends on `common`, so... I suppose the answer is yes. It will definitely depend on `common`.

Haha, I guess the `jvm` target was a bad example. But if you were to rename a native target, for example, would it still get connected to the hierarchy in the same way?

(Personally I'm hoping the default hierarchy template will adopt a shared JVM + Android intermediate source set eventually!)

I believe you should be able to rename targets and keep using the hierarchy, yes.