Compose integration question: for teams that use s...

# compose

[Tash]

Compose integration question: for teams that use static analysis tools like detekt, etc the introduction of Compose and it’s conventions might violate a lot of rules that come with “vanilla” Kotlin programming, such as long parameter lists, “magic number”s in dp declarations, top level constants named in PascalCase etc., that we see used in the Compose source code. Is Compose declarative-tree style programming heralding a new set of coding styles/conventions for Kotlin? Wondering if anyone has had to justify “this is how its done in Compose” with regards to style/convention to their coworkers who may not be too familiar with Compose just yet.

[ephemient]

make sure they read https://github.com/androidx/androidx/blob/androidx-main/compose/docs/compose-api-guidelines.md ?

[Tash]

👍🏼 Yeah came across that, definitely essential reading. Was hoping to find something more around other Kotlin language conventions that might evolve in Compose land