3 ms·
I came across that annoyance in Android code where there were 30 some View fields of different types, TextView, ImageView etc. It wasn't my code so I didn't kno
by guelo 10y ago
I came across that annoyance in Android code where there were 30 some View fields of different types, TextView, ImageView etc. It wasn't my code so I didn't know what names had been used but I knew that I wanted to find one of the TextViews.
In Java Android code we normally group the fields by type to make them easier to find. But maybe we need a different convention for Kotlin.
- Larrikin 10y agoFor Android UI components specifically I usually just include the type in the name. The types can get a little long but when you need to have and operate on userNameTextView userNameTextInputLayout you end up saving time when looking back