https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
s

Stylianos Gakis

01/26/2023, 3:26 PM
Is there any standard regarding file naming for KMP projects? I’ve seen that for example inside androidx, for compose which provides common/android/desktop support, like here, for example for the android target of material3, they have some (most in this case) files named like “[filename].android.kt” and others just “[filename].kt”. I did check, and it’s not only the ones that do also have a identically named file in the common target, as for example “DatePickerDialog.android.kt” only exists for the android target and is not present in the common directory to require the .android disambiguation there. Yet “SearchBar.kt” doesn’t have it, which is also android-only. And it’s also not that
DatePickerDialog
has any expect/actual keywords or whatnot. So I guess my question is, I’ve seen this “[filename].[platformname].kt” naming convention, but is it specified somewhere how the decision to add the [platformname] is made?
j

jw

01/26/2023, 3:30 PM
It's only needed for the JVM/Android because of the concept of a
.class
and the inability to produce duplicate names. And it's only required when you have the same-named files in common and a jvm or android source set AND those files have top-level declarations (i.e., will produce a classfile with the name
FilenameKt.class
.
I would not pervasively adopt such a system but rather employ it only when necessary. And the easiest way to employ it is only in those jvm or android source sets and only when there is a collision which fails the build.
s

Stylianos Gakis

01/26/2023, 3:32 PM
Perfect, so what you are saying is that if there is a problem to be had, I will know in compile-time regardless. Does one need to do something special to bring those collisions to the surface and have the build fail, or will it just happen, in which case I will know that this is the solution?
j

jw

01/26/2023, 3:36 PM
You will see something like this:
> Task :mosaic-runtime:compileKotlinJvm FAILED
e: file:///Volumes/dev/JakeWharton/mosaic/mosaic-runtime/src/commonMain/kotlin/com/jakewharton/mosaic/platform.kt:1:1 Duplicate JVM class name 'com/jakewharton/mosaic/PlatformKt' generated from: PlatformKt, PlatformKt
e: file:///Volumes/dev/JakeWharton/mosaic/mosaic-runtime/src/jvmMain/kotlin/com/jakewharton/mosaic/platform.kt:1:1 Duplicate JVM class name 'com/jakewharton/mosaic/PlatformKt' generated from: PlatformKt, PlatformKt
The conditions when it happens are even more rare than I stated. You can actually have top-level declarations in both files if they are all `expect`/`actual`.
s

Stylianos Gakis

01/26/2023, 3:38 PM
Awesome, thank you a lot for making this make sense for me! So as I am understanding, a lot of these .android. in particular in that m3 file are not actually necessary. But they may be doing it out of convention at this point. For our project, I will simply not do it unless we need to, sounds like a sensible solution for now.
l

Landry Norris

01/26/2023, 3:38 PM
iOS also required this if there were any files with a matching name at all when using the compose-jb main method, since that would copy files to the resulting binary. If two had the same name, XCode would fail the build.
I’m not sure if this is still the case, as I switched to cocoapods and an XCode project instead of using the compose-jb packaging.
c

CLOVIS

01/26/2023, 3:54 PM
At least for the JVM, another solution than renaming the file is to add
@file:JvmName("FileNameJvm")
at the start of the file. Not sure if it works for Android
j

jw

01/26/2023, 3:59 PM
It does. All of Android goes through class files the same as the JVM.
l

Landry Norris

01/26/2023, 3:59 PM
Excluding androidNative* targets, of course.
e

eygraber

01/26/2023, 4:35 PM
Despite not needing to do it, I've been naming my files like that because it conveys meaning to what the file is
l

Landry Norris

01/26/2023, 4:39 PM
It also makes it much easier to figure out which file is which platform when making expect/actuals. A lot of times, I have to scroll up to the top to find imports. When the file is Foo.android.kt, I can easily see.
j

jw

01/26/2023, 4:45 PM
The source set folder conveys the meaning of what target the platform is for. If you are always going to suffix the file then put them all in a single folder and use globs to assign them to target source sets. Otherwise are redundantly specifying the intended platform.
e

eygraber

01/26/2023, 4:46 PM
I usually search to open files, and the file extension is easier to eyeball than the source set folder
l

Landry Norris

01/26/2023, 4:46 PM
I find that the little tab doesn’t always show the source set for repeat files, especially if the files with the same name have a slightly different folder structure.
Also, search. That font they use for the source set/module name gets hard to see with my less than great vision.
j

jw

01/26/2023, 4:50 PM
You should turn off tabs! In the latest IntelliJ I get both the source set name and the file name in the top bar.
l

Landry Norris

01/26/2023, 5:32 PM
That’s what I was referring to. If the folder structure doesn’t match, you see the last difference, such as foo/blocking.kt and bar/blocking.kt instead of androidMain/blocking.kt and commonMain/blocking.kt. One could argue that the folder structures should match, but that doesn’t make sense in 100% of situations.
j

jw

01/26/2023, 5:34 PM
That seems like useful feedback for the IntelilJ team. The source set is probably important enough to always be displayed whenever there are multiple source set folders in use.