Colton Idle
06/02/2021, 11:44 PMbuildFeatures {
buildConfig = true
compose = true
viewBinding = true
}
Igor Demin
06/03/2021, 7:33 AMorg.jetbrains.compose
plugin with compose = true
But it seems work.
Theoretically there can be a version conflict. Because compose = true
applies its own version of Compose Compiler plugin (kotlinCompilerExtensionVersion) that can be different from compiler plugin that is applied by org.jetbrains.compose
But this property also adds some other features like preview in Android Studio and (probably, not sure) icons in the gutter.Colton Idle
06/03/2021, 1:00 PM// It is needed, because 'org.jetbrains.compose' artifacts are the same artifacts as 'androidx.compose'My team is happy to hear that the artifacts are the same its just the package name that's different.
Igor Demin
06/03/2021, 1:06 PMis basically a 1:1 with android composeYes, in terms of code it should be identical in android. JB android artifacts just built from a different revision, with a different flag (mppSupport=true) and published by different maven coordinates.
Igor Demin
06/03/2021, 1:20 PMandroidx-main
revision) they can be unstable in compare to stable androidx
artifacts (for example, the future androidx 1.0.0)Colton Idle
06/03/2021, 1:43 PMJB android artifacts just built from a different revision, with a different flag (mppSupport=true) and published by different maven coordinates.That's perfect! Exactly what I think will convince my team. We just wanted to make sure there wasn't some crazy changes being made. But if it's just a different revision, added mppSupport flag and different coordinates... that should convince them! Thank you again!