IssueTracker

Builders were great pattern in Java, however in Kotlin I have always felt they are no longer needed with default parameters or can be written a little more cleanly using higher order functions as opposed to the following.

val constraints = Constraints.Builder()
            .setRequiresCharging(true)
            .setRequiredNetworkType(NetworkType.CONNECTED)
            .build()

The default parameters approach is trivial using a data class and named parameters could be used when being constructed.

data class Constraints(
    val requiredNetworkType: NetworkType = NetworkType.NOT_REQUIRED,
    val requiresCharging: Boolean = false
)

val constraints = Constraints(requiredNetworkType = NetworkType.METERED)

For converting the builder from java to a more idiomatic Kotlin, we could also write a function that uses a method with a receiver on the builder.

inline fun constraints(builder: Constraints.Builder.() -> Unit): Constraints {
    return Constraints.Builder().apply { builder() }.build()
}

val constraints = constraints {
   setRequiredNetworkType(NetworkType.CONNECTED)
   setRequiresCharging(true)
}

The naming of these could probably be renamed, just a nicer way to write builder like classes in kotlin.