Okay, this is going to sound dumb but I'm using co...
# compose-ios
c
Okay, this is going to sound dumb but I'm using compose multiplatform in one project in a tiny tiny little module. We're on compose-plugin = "1.5.11" and I want to update to 1.6.0-rc01. Do I just update that version string and that's it? I updated and hit run and everything works... im just surprised.
1
I just kinda dont know whether i should be udpating the other compose dependencies too?
and how that interacts with the versions listed on the compose multiplatform release notes
Hm. I guess it didn't work because even though I added a font, a
Res
file isn't auto generated for me.
my design system module build file
Hm.
./gradlew :my-design-system:generateComposeResClass
succeeds... so that's good? i guess its picking up the resource stuff from 1.6.0?
This might help with resources
c
thanks...
could it be
I was just missing implementation(compose.components.resources) 🤯
😉 1
yep. i think that was it. im still a bit confused because it says I can't call
Font(...)
without being in a composable, buti never had my font declarartions in a composable before
Weird. I'm setting up custom fonts as shown in the compose samples here: https://github.com/android/compose-samples/blob/7f8137b763f5f8ef238bdeecd1e922a4c6[…]etsnack/app/src/main/java/com/example/jetsnack/ui/theme/Type.kt But that doesn't seem to be possible with kmp compose fonts?
fuck yeah. got it. just followed this instead. not too fun because i had to refactor a bunch of things. but it works now. https://developer.android.com/jetpack/compose/designsystems/custom#implementing-fully-custom
a
Awesomeness, I figured it was probably just the dependency 😁
c
i of course looked at two different tutorials and just didn't RTFM. thanks andrew!
🙌🏻 1
a
No problem 😄