What id name convention is good for Kotlin android extensions

Question

Using Kotin android extensions I can avoid using findViewById, but Im not sure how to name the ids to use it propertly.

I found two options are:

1. Use simple names for ids but then I can get in trouble with espresso if I use it with fragments:

android.support.test.espresso.AmbiguousViewMatcherException: 'with id: .../mainLayout' matches multiple views in the hierarchy.

It is because I have two fragments inside a TabLayout with same ids:

<LinearLayout android:id="@+id/mainLayout"

2. Name with owner: "@+id/loginMainLayout" and "@+id/signUpMainLayout"

But then I will have to use variables like signUpMainLayout.doSomething().

Note: I dont like the use of _ in this case since that's not a good code style.

What other options are?

Answer 1

I can't recognize why you don't use "@+id/loginMainLayout" and "@+id/signUpMainLayout" when the name is in lowerCamelCase that is common in Kotlin and Java. The use case will be signUpMainLayout.doSomething() as you said.

Anyway It's a good practice to use unique names for id's in whole app. it's not because of Espresso but mainly to know where the view associated with an ID when you see the name of ID. It's not hard if you use this style. Example:

In fragment_contacts:

<TextView id="+id/contactNameText 
android:text="John Smith" .../>

<ImageView id="+id/contactUserImage .../>

Assert: There is Image in contactUserImage because to know it's an ImageView.

In fragment_settings:

<TextView id="+id/settingsNotificationText 
android:text="Turn notifications on/off" .../>

<checkBox id="+id/settingsNotificationCheck .../>

Answer 2

in my case, I have been working using this convention https://jeroenmols.com/blog/2016/03/07/resourcenaming/, but without the underscores and in camel case convention.

If you notice when you drag a control to a view, within android studio, it names the id using the camel case convention.

And although the names of the variables may be a bit large, you can always use val or var in the declaration of the variable.

regards