Is this not required for Compose 1.0 anymore? Seems to build just fine without it. ``` composeOptio...

# compose

[Zach Klippenstein (he/him) [MOD]]

Is this not required for Compose 1.0 anymore? Seems to build just fine without it.

composeOptions {
    kotlinCompilerExtensionVersion "…"
  }

[eygraber]

I think that's been optional for a while now.

[Zach Klippenstein (he/him) [MOD]]

Huh, somehow i missed that memo

[Tash]

that’s weird, I’d get comp errors citing wrong Kotlin version on rc1/2 without it…there are a few threads from last month etc that talk about that

[Tash]

but maybe its not needed with 1.0+

[eygraber]

I haven't had it for a while now ¯\_(ツ)_/¯

[Colton Idle]

I don't think it was deprecated? The other composeOption was deprecated a while back though AFAIK

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1614672032411500

[Colton Idle]

Zach, just tried removing it in 1.0.1 and it worked fine, but then upgraded to 1.1.0-alpha01 and removing it caused issues. something about the compiler being on 1.0.0-beta07 /shruggie

[Zach Klippenstein (he/him) [MOD]]

Curious

[CRamsan]

Same for me. I remember all other option being deprecated but not kotlinCompilerExtensionVersion. I had the same issue as Colton when I removed it.

[julioromano]

kotlinCompilerExtensionVersion is not deprecated. I suppose if omitted it defaults to the last compose version hardcoded in the android gradle plugin. So YMMV. If the agp default is compatible with the other compose artifacts you depend on then your build won’t break.

[eygraber]

Maybe I haven't been using it because I pretty much only use the Jetbrains compose artifacts 🤔

[Chris Sinco [G]]

@nosuid might have more context. I notice we still have it in our Compose project template in Android Studio, so probably should update the template as well if things have changed.