While it is expected to have duplicate content roots registered in the import process, it's not expected that they both show the app project as their base path.
We add the basic starter assets directory as a resource directory for JS and JVM source sets.
Therefore it gets registered twice in the IDE upon import. Gradle is smart enough to consolidate behind the scenes and so is the IDE, but the IDE lets you know about it.
If my memory serves me, we took this approach because that's how Kotlin MPP handles propagating common resources to its platforms, but this might have changed or might not be true.
Things to try:
[ ] verify studying/asking how Kotlin MPP propagates common resources
[ ] adding the basic starter assets directory as a common module resource directory
Things to do (if applicable):
update documentation to include info about the error
While it is expected to have duplicate content roots registered in the import process, it's not expected that they both show the app project as their base path.
We add the basic starter assets directory as a resource directory for JS and JVM source sets. Therefore it gets registered twice in the IDE upon import. Gradle is smart enough to consolidate behind the scenes and so is the IDE, but the IDE lets you know about it.
If my memory serves me, we took this approach because that's how Kotlin MPP handles propagating common resources to its platforms, but this might have changed or might not be true.
Things to try:
Things to do (if applicable):