[DISCUSSION] Use Kotlin Android Extensions instead of Butterknife

[macgills]

Summary:

In kotlin we have the option of using Kotlin Android Extensions ViewBinding

I am in favour of their usage for their ease of use.

The alternatives are:

1. Continue using butterknife
2. Use ViewBinding for compile time safety

[maskaravivek]

I am in favour of using Kotlin Android Extensions ViewBinding for all the Android components that are written in Kotlin.

IMO our goal should be to gradually remove all usages of Butterknife. Whenever an existing Android component which is written in Java is converted to Kotlin, we should ideally replace Butterknife with Kotlin Android Extensions ViewBinding.

Let's wait for what others think about this and then we can make this part of our contributor guidelines.

[misaochan]

Whenever an existing Android component which is written in Java is converted to Kotlin, we should ideally replace Butterknife with Kotlin Android Extensions ViewBinding.

This sounds good to me.

[maskaravivek]

@misaochan Do we need to wait for more opinions on this or if everyone agrees then we can unblock #3524.

[misaochan]

Let's just get @ashishkumar468 's opinion, we should be good after that since this is a relatively minor policy.

[ashishkumar468]

Agree with @maskaravivek 's opinion, I am okay to go with this, read the docs, supports both View Caching and Layout Containers (so that classes like ViewHolders can also be used as an extension container).

[macgills]

A minor xml style point now that it seems we are all in agreement.

Should we start writing our ids in camelCase instead of snake_case seeing as they will be present in Kotlin classes?

[ashishkumar468]

I think that should be okay.

[macgills]

@maskaravivek if you are okay with it then I will consider this issue closed

[maskaravivek]

Once the liked PR is merged, we can close this issue.