github/compose-jb - compose-jb - 帆软第三方插件仓库

Author	SHA1	Message	Date
Oleksandr Karpovich	93b513458d	Update for k/wasm (#4009 ) This a comanion PR to https://github.com/JetBrains/compose-multiplatform-core/pull/914 Resources lib doesn't contain k/wasm target yet. It will be added in a separate PR --------- Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>	6 months ago
dima.avdeev	679f2821c0	iOS cache kind warning to error (#3667 ) Co-authored-by: Alexey Tsvetkov <alexey.tsvetkov@jetbrains.com>	9 months ago
Alexey Tsvetkov	950d5a991c	Manage Kotlin native cache kind automatically based on Kotlin version (#3477 ) Set Kotlin/Native cache kind based on Kotlin version Resolves #2046 Resolves #2386	10 months ago
Igor Demin	bf958eb510	Improve DSL for setting a custom Compose Plugin (#2527 ) * Improve DSL for setting a custom Compose Plugin Fixes https://github.com/JetBrains/compose-jb/issues/2459 Readme: https://github.com/JetBrains/compose-jb/pull/2526 1. Add `dependencies: Dependencies` extension that is accessible in `compose { }` block 2. Add `Dependencies.compiler` property that can return versions of Compose compiler used by the plugin: ``` compose { kotlinCompilerPlugin.set(dependencies.compiler.forKotlin("1.7.20")) //kotlinCompilerPlugin.set(dependencies.compiler.auto) // determined by applied version of Kotlin. It is a default. } ``` 3. Add ability to set arguments for Compose Compiler. Now we can write: ``` compose { kotlinCompilerPlugin.set(dependencies.compiler.forKotlin("1.7.20")) kotlinCompilerPluginArgs.add("suppressKotlinVersionCompatibilityCheck=1.7.21") } ``` 4. Remove checks for different targets We had a separate check for JS, when we released 1.2.0. It doesn't support Kotlin 1.7.20 at that moment. It is hard to refactor this feature in the new code, so I removed it. It is not needed now and it had an ugly code. When we will need it again, we'll write it again. 5. Remove the `compose.tests.androidx.compiler.version` property from gradle.properties and remove `defaultAndroidxCompilerEnvironment` Because they are used only in one test, and it seems there is no reason to use it in another place in the future * Discussions	1 year ago
Igor Demin	3996233b03	Allow to use Compose on multiple Kotlin versions (#2366 ) JS target supports a lower version (1.7.10), because we have a bug in Koltin 1.7.20 Compose 1.2.0 will support: 1.7.20 and 1.7.10 for Android and Desktop 1.7.10 for JS We will release the new patchset (1.2.1) with 1.7.2X support for JS later	2 years ago
Alexey Tsvetkov	58b0a22fb5	Allow customizing Compose compiler plugin (#2347 ) By default, the Compose Multiplatform Gradle plugin uses `org.jetbrains.compose.compiler:compiler:<COMPOSE_VERSION>` as a compiler plugin . However, a new version of Kotlin might be incompatible with the default version of compiler plugin. Previously, that forced users to update to a new version of Compose Gradle plugin & Compose libraries in order to use a new version of Kotlin. Accordingly, Compose framework developers had to release a new version of all libraries, when a new version of Kotlin is released. Some time ago the Compose team at Google made it possible to update a compiler plugin without updating the Gradle plugin and/or all Compose libraries https://developer.android.com/jetpack/androidx/releases/compose-kotlin This change allows to specify a custom compiler artifact by using the following DSL: ``` compose { kotlinCompilerPlugin.set("<VERSION<") // or kotlinCompilerPlugin.set("<GROUP_ID>:<ARTIFACT_ID>:<VERSION>") } ```	2 years ago