nico: I feel some of your pain too, the `internal`...
# announcements
c
nico: I feel some of your pain too, the
internal
side in particular is not super intuitive for me, especially how it interacts with
kotlinc -module-name
. For what it's worth, in Kobalt, I ended up breaking the whole thing in multiple projects. It's the only way to make sure unrelated modules don't use symbols they're not supposed to (more specifically,
kobalt-plugin-api
contains symbols only plugin users should see and then
kobalt
is the application and it depends on it