New Compose BOM release! <https://android-develop...
# compose
b
p
c
Oooooh. very interesting
Compose compiler 1.5.5 introduces a new compiler option to provide a configuration file for what your app considers stable. This option allows you to mark any class as stable, including your own modules, external library classes, and standard library classes, without having to modify these modules or wrap them in a stable wrapper class.
What does this mean for the new experimental flag for ~disabling all stability annotations, etc. Is that experimental project killed or is that still the long term plan?
lmao. kept reading the article where it talks about strong skipping mode.
b
Strong skipping mode doesn't disable stability annotations, it just changes one of the main reasons you would have to use them. There will still be cases where you need to mark something as stable though so both features work in tandem
c
Nice, good to know! I hope that we can really start to think about them less. I've shipped 5 100% compose apps to millions of users, and have used @Stable exactly 0 times. lol