https://kotlinlang.org logo
Join Slack
Powered by
None of the 1.6 change logs have thus far mentione...
# compose-web
j
None of the 1.6 change logs have thus far mentioned that decoy generation was disabled and that recompilation of downstream libraries is required for JS targets. Please include it in the final 1.6 change log!
🙏 1
Or I just missed it, because I was mostly looking for "decoy" but no one would know wtf that is so it's probably not mentioned as such...
a
What is it ? x)
j
It was a workaround for a Kotlin semi-bug in like 1.3 that was fixed in 1.4 (or something like that, i don't recall the timelines)
But since it's an ABI change we kept generating these decoys as the compilation mode of Compose or it would break everyone
but since the workaround was no longer needed at some point it makes sense to disable them, and Compose 1.6 is that time
👍 2
Anyone who is running the Compose compiler themselves on JS will know what it is because they will have had to enable them to get compilation to work. Now those people have to go and remove that flag. It's really easy, I just want to make sure it's called out. Here's an example: https://github.com/cashapp/molecule/commit/e4d20769a95222fef130251e150f594de7499ae5
k
cc @Igor Demin
h
So it does effect all compose JS libraries?
o
yes, it affects all compose k/js libs. Those which use compose-multiplatform-gradle plugin don't really need to do anything, the change is applied automically
To rephrase: The compose k/js libraries need to be rebuilt with a dependency on 1.6.0 in order to be used in projects with new 1.6.0
i
Added to the changelog: https://github.com/JetBrains/compose-multiplatform/releases/tag/v1.6.0 (search for 
Web (k/js)
) Thanks!
j
Thank you!
s
@Igor Demin special for the stable to stable release and for example 1.6.0-rc01 already had that change? Or this is starting from 1.6.0 stable ?
o
1.6.0-rc01 already had that change
yes, beta and rc had this change too
7 Views
Open in Slack
PreviousNext
Powered by