Noob question, I have a class called EntityUUID. o...

# getting-started

[Tara Czutno]

Noob question, I have a class called EntityUUID. or should it be EntityUuid?

[Johann Pardanaud]

Name it like you want, but keep it consistent across your codebase 🙂

[Johann Pardanaud]

Personally, I would go with EntityUuid because if you need to add a suffix it is way more readable. Compare EntityUUIDSuffix and EntityUuidSuffix and choose what you prefer.

[Tara Czutno]

Yeah that makes sense

[ephemient]

I'd always use titlecase for any words within camelcase names, because Kotlin follows JavaBeans property naming conventions, which leads to getUUID() = val UUID, getUuid() = val uuid

[ephemient]

tl;dr EntityUuid

[Giorgi]

https://kotlinlang.org/docs/coding-conventions.html#choose-good-names

[Youssef Shoaib [MOD]]

For the future, these questions fit better in #naming

[geepawhill]

(I'm too late to this party, but I just can't help myself: every time you capitalize an abbreviation in an identifier, a devil gets its horns.)

[Klitos Kyriacou]

There are some names from java.net which are inconsistent within themselves, such as HttpURLConnection.

[Arun M]

When using an acronym as part of a declaration name, capitalize it if it consists of two letters (IOStream); capitalize only the first letter if it is longer (XmlFormatter, HttpInputStream).