With Kotlin 2.0 and the New Kotlin Compose Compiler Should we have ```buildFeatures { compose = ...

# compose

[Vaibhav Jaiswal]

With Kotlin 2.0 and the New Kotlin Compose Compiler
Should we have

buildFeatures {
    compose = true
}

in CMP modules ?
This allowed LayoutInspector to work even in CMP Projects
If not then how can we use Layout Inspector ?

[Konstantin Tskhovrebov]

The config is a part of AGP. And the layout inspector is a part of Android Studio. So, yes, as I know

[Vaibhav Jaiswal]

And this wont mix up Jetbrains Compose Compiler and Jetpack Compose compiler?

[mohamed rejeb]

That would be a good thing to have, please let us now if the inspector works for your with CMP and AS

[Vaibhav Jaiswal]

I was using this before I migrated to Kotlin 2.0
And it worked pretty good

[mohamed rejeb]

That’s good to hear, I remember I tried it before and I didn’t manage to make it work. I will check it.

[Konstantin Tskhovrebov]

https://androiddev.social/@terrakok/112416852159900839

[Vaibhav Jaiswal]

without compose = true
All i see is this
And none of my composables

[Vaibhav Jaiswal]

With compose = true
Everything works
But should we enable this?
Would it create problems for the Jetbrains Compose Compiler???

[Albert Chang]

If you just want the layout inspector to work, I think you can also use this:

composeCompiler {
    includeSourceInformation = true
}

Setting buildFeatures.compose = true also enables previews in android source sets.
What problems are you imagining?

[Vaibhav Jaiswal]

Not any as such
Let me try this

[Ben Trengrove [G]]

Yes, please do keep the compose = true part. It won't cause problems for the compiler

[Vaibhav Jaiswal]

Which to keep
includeSourceInformation or compose = true ?

[Vaibhav Jaiswal]

both works

[Albert Chang]

depends on whether you need AS specific features like previews and live literals.

[Vaibhav Jaiswal]

Just need LayoutInspector