Do you think it's ok in this case?

# announcements

[LeoColman]

Do you think it's ok in this case?

[Adam Powell]

Personally I went the other way and started PascalCasing my enums instead

[Adam Powell]

precedent here in ktor: https://github.com/ktorio/ktor/blob/master/ktor-http/common/src/io/ktor/http/HttpStatusCode.kt

[LeoColman]

interesting

[LeoColman]

very interesting actually xD

[Adam Powell]

also other public `val`s for the same reason; when you put them next to `object`s and sealed classes, as you've found, there doesn't seem to be much reason to leak the implementation details in the naming convention

[Adam Powell]

it still seems kind of contentious when it comes to things like MAX_VALUE-type things that can be declared with const val and the official kotlin style guide is kind of vague on this

[Adam Powell]

https://kotlinlang.org/docs/reference/coding-conventions.html#property-names

[Adam Powell]

it permits both styles but it's not something so prescriptive that you could use linters to settle debates

[karelpeeters]

Same here, PascalCase for most enums.

[LeoColman]

That's very interesting

[LeoColman]

linters complain about pascal case too, tho

[karelpeeters]

Just turn that off, we're not here to serve the linter!

[LeoColman]

I know hahaha

[LeoColman]

I just wanted to know if it was a bad thing