Out of curiosity: the official guidance around Gra...

# multiplatform

[Marcello Galhardo]

Out of curiosity: the official guidance around Gradle modules are kebap-case (2) but when you generate a new project with KMM plugin, it uses camel case (ie, androidApp, iosApp and shared). Any special reason for that? Should we use camel case to all “kotlin multiplatform modules” as a standard or only for the app modules?

[Casey Brooks]

When publishing libraries from Gradle, by default the artifact coordinates are derived from the project name, and since the convention for Maven coordinates is kebob-case, it makes sense for library modules to also be named in kebob-case.

For application modules, since they're not published to MavenCentral or anything, the project name really doesn't impact much. I'm not sure why the KMM plugin generates projects in camelCase, but it doesn't strike me as too terrible, though personally I would probably rename the modules to be kebob-case to follow the Gradle convention and to avoid any potential issues with filesystem case-sensitivity

[danprado]

Interesting. I seem to have a bug with the plugin when generating modules using kebab-case where it generates 2 podspec files: 1 named kebab-case.podspec and 1 named kebab_case.podspec.
I thought that could be related somehow. I guess I can just go with kebab case and delete the second podspec file.