Allow enabling compose compiler per target in multiplatform module

[mgroth0]

Consider a project with a single multiplatform module with a js target for frontend and a jvm target for backend. This module might want to only enable the compose gradle plugin, compose compiler, and compose dependencies for the JS target and completely leave out compose for the jvm target.

This is discussed in #1568. But it seems that issue is being treated as a question and not an enhancement proposal. So here I am making the proposal that the Compose Multiplatform Gradle Plugin allows developers to toggle compose per Kotlin Multiplatform target within a single module.

[eymar]

Will this solution work for you? #3722 compose.platformTypes

[mgroth0]

Thanks, It definitely helps a lot! It likely will resolve all the practical issues I have for now.

Just curious though, what is stopping us from implementing control at an even finer level of granularity such as per source set or per gradle configuration?

[eymar]

Not sure that configuring it per source set is possible at all. The source sets can't be compiled independetly. All relevant source sets get "combined" to compile for a particular target, and if a target declares to apply the Compose plugin, it means it's applied to all code (involved source sets).

And as for gradle configurations, I'm not sure I understand how it can affect the logic to apply or not apply the plugin.
I guess we can only decide to apply or not based on the target type or target name.

[mgroth0]

I realize I misunderstood some terminology. You mentioned in your PR you can have

jvm("backend) {}
jvm("frontend") {}

Which you referred to as multiple "targets". I thought these were called source sets, but I think I was wrong here.

This can be closed I think? Thank you.

[eymar]

Yes, those are 2 jvm targets with different names.

Sure, let's close it.

[okushnikov]

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.