Is there any reason for this inspection that was added to the 2023.2 Intellij EAP? It's a relatively...

# naming

[asdf asdf]

Is there any reason for this inspection that was added to the 2023.2 Intellij EAP? It's a relatively common convention to use PascalCase for constants instead of SCREAMING_SNAKE

[ephemient]

officially https://kotlinlang.org/docs/coding-conventions.html#property-names and https://developer.android.com/kotlin/style-guide#constant_names

[ephemient]

although that specific convention is rejected by https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-api-guidelines.md#singletons_constants_sealed-class-and-enum-class-values so blob shrug

[louiscad]

I think you meant SCREAMING_SNAKE

[czuckie]

SCREAMING_CAMEL would be an impossibility right? Camel case is an uppercase letter at the beginning of subsequent words in a single symbol... I get so confused. I didn't realise BlahBlah was Pascal case for example.

[ephemient]

if all your identifiers are only 1 letter long, they can be both CamelCase and SNAKE_CASE at the same time

[Javier]

there is a thread to add this convention to the official ones, but don't remember in which channel

[asdf asdf]

Oops lol, yeah meant snake

[asdf asdf]

Think this was the thread https://kotlinlang.slack.com/archives/CQ3GFJTU1/p1679332632581359

[dewildte]

WHY_U_NO_LIKE_THE_YELLY_NOPE_ROPE_CASE????!!!!!

[dewildte]

🧌