Hey all - for those who were asking about Kotlin `...
# compose
n
Hey all - for those who were asking about Kotlin
1.6.10
support, we shipped Compose Compiler
1.1.0-rc02
with official support for Kotlin
1.6.10
(see https://developer.android.com/jetpack/androidx/releases/compose-compiler#1.1.0-rc02). Additionally, we also started publishing a table mapping the Compose Compiler version to it's compatible Kotlin version. (https://developer.android.com/jetpack/androidx/releases/compose-kotlin)
๐Ÿ• 8
๐ŸŽ‰ 10
๐Ÿ‘๐Ÿฝ 1
๐Ÿ‘ 17
jetpack compose 9
๐Ÿ‘๐Ÿผ 1
K 9
c
That mapping is ๐Ÿ’ฏ Also, thanks for getting an update out quickly. 1.6.0 of kotlin had a bunch of issues so being able to get onto 1.6.10 without a snapshot is amazing.
๐Ÿ‘ 2
๐Ÿ‘๐Ÿผ 1
j
judging from https://github.com/android/compose-samples/pull/716/files it looks like versions will line up again in rc03
Copy code
- kotlinCompilerExtensionVersion Libs.AndroidX.Compose.version
+ kotlinCompilerExtensionVersion '1.1.0-rc02' // For Kotlin 1.6.10. Revert with rc03
n
Only the Compose Compiler received the
1.1.0-rc02
update, so all other Compose libraries will remain at
1.1.0-rc01
.
The general no-guarantees plan is to re-align versions at
1.1.0-rc03
, if we need a rc03 ๐Ÿ™‚. As an aside, we managed to keep all Compose libraries in sync until now, but in the future, we do expect more version splits. It let's us ship faster updates to parts of Compose and removes 'empty' updates (versions without any changes)
m
And what will help us to keep the builds consistent? This all starts to become a 1000 pieces puzzle.
๐Ÿ‘ 2
๐Ÿ’ฏ 1
c
Can compose team consider using gradle BOM like firebase?
๐Ÿ‘ 2