Back in the day, enums followed the `VERY_BOLD` na...

# compose

[Zoltan Demant]

Back in the day, enums followed the VERY_BOLD naming pattern, since compose they (and a lot of other variables) follow a MuchSofterPattern. Im curious about how you manage any type of consistency between the two in your projects? Personally, I prefer the latter - but refactoring isnt very simple when the old style enums are part of external datasets, json structures, etc. I feel liek Im stuck with UPPER_CASE and BeautifulCase (sorry, I couldnt find the actual appropiate names for them) and I rarely know when to use which as a result.

[Kirill Grouchnikov]

The Kotlin one is camel case

[darkmoon_uk]

The other one is called SCREAMING_SNAKE_CASE (Really).