Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kotlin 1.7.20-compatible release #125

Closed
JakeWharton opened this issue Sep 29, 2022 · 4 comments · Fixed by #129
Closed

Kotlin 1.7.20-compatible release #125

JakeWharton opened this issue Sep 29, 2022 · 4 comments · Fixed by #129

Comments

@JakeWharton
Copy link
Collaborator

JakeWharton commented Sep 29, 2022

Tracking issue.

Blocked by JetBrains/compose-multiplatform#2349

@mhernand40
Copy link
Contributor

Would it be feasible to get a 0.4.1 release that doesn't use JetBrains Compose? We're seriously considering using Molecule for our Android project and just updated to Kotlin 1.7.20. 🙂

@JakeWharton
Copy link
Collaborator Author

The JS target is the problem and the last version which did not support JS was 0.2.0 so doing any kind of stable release would entail dropping platform support.

If there is not a .21 within two weeks or so I may consider releasing an 0.6.0 build with a qualifier like "nojs", but I would prefer the pressure remain on JetBrains to correct this problem.

@JakeWharton
Copy link
Collaborator Author

You are free, however, to depend only on the Molecule runtime and add the Android Compose compiler which supports Kotlin 1.7.20. Simply do not use our Gradle plugin and that configuration should work fine.

@mhernand40
Copy link
Contributor

You are free, however, to depend only on the Molecule runtime and add the Android Compose compiler which supports Kotlin 1.7.20. Simply do not use our Gradle plugin and that configuration should work fine.

Sweet! That actually works for me. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants