How do you deal with ios people complaining about ...

# multiplatform

[ursus]

How do you deal with ios people complaining about naming schemes? i.e. CustomerId vs CustomerID?

[streetsofboston]

Are the iOS devs on your team complaining, or iOS devs on social media/slack?

[streetsofboston]

If the latter, if that is all they complain about, then they have a pretty good dev life 🙂

[Frank Bouwens]

Talk with them about creating a coding-convention;

See:
https://kotlinlang.org/docs/coding-conventions.html#source-file-names

[ursus]

yes devs on my team, they talk that the interface provided is not swifty - when called from swift

[streetsofboston]

They are not wrong, but iOS devs at my work have gotten used to it.
The kotlin-to-swift interface (naming) is not yet optimal. But using KMP's potential saving is likely to outweigh these issues.

[ursus]

Is there a way to maybe rename it for them? i.e. some annotation or something

[Seb Jachec]

You can annotate to provide a Swift or ObjC name, although you might find that clutters things a little.

@ObjCName(swiftName = "customerID")
val customerId: String

https://kotlinlang.org/api/core/kotlin-stdlib/kotlin.native/-obj-c-name/

[streetsofboston]

https://kotlinlang.org/docs/native-objc-interop.html#change-declaration-names
Ah.... Seb already posted that answer 🙂

[ursus]

oooh great

[Mez Pahlan]

Tell them the compiler doesn't care about your naming conventions so get used to it 😆

[ursus]

I gotta appease them somehow in the beginning 😄

[Julian Pellico]

You could point out that "ID" is not an acronym (it's an abbreviation for identity or identifier), and thus the 'D' shouldn't really be capitalized. Apple made a mistake in capitalizing it in their frameworks e.g. CoreData. 🙂