Suppose i have 3 libraries: shared, ui, server. Sh...
# compose
p
Suppose i have 3 libraries: shared, ui, server. Shared is needed for declaring model classes that are used by ui and server. For shared and ui i want to apply Compose plugin to 'prepare' classes for Compose at compile time (stability checks, etc). Question: do i need runtime Compose dependency for server (that will be not using Compose logic) to be able to work with shared classes after Compose compiler transform them?
s
I would suggest thinking more on why your shared library needs to publish compose dependencies downstream. This likely isn't necessary
p
Just want to let Compose do some preparations at compile time. To perform better at runtime.
c
I guess what @Seri means is that you share network models which should not be used in your UI layer. The compose annotations for stable and so on should go to your domain models.
p
I understand that, but some classes are shared anyway. The question was not about that.
s
If this is just about stability, you can mark classes as stable or not through that file that you can write the fully qualified names of those classes in. No need to apply the compose compiler there.