Daniele Segato
02/18/2019, 4:45 PMtddmonkey
02/18/2019, 4:50 PMCzar
02/18/2019, 4:53 PMDaniele Segato
02/18/2019, 5:03 PMcopy
?tddmonkey
02/18/2019, 5:23 PMsnowe
02/18/2019, 5:26 PMdata class AssetReturnValueObject(
val assetId: AssetId?,
val candidateAssetId: CandidateAssetId?,
val qualifyingAssetId: QualifyingAssetId?,
val qualifyingAssetAdjustmentId: QualifyingAssetAdjustmentId?
) {
class Builder {
private var assetId: AssetId? = null
private var candidateAssetId: CandidateAssetId? = null
private var qualifyingAssetId: QualifyingAssetId? = null
private var qualifyingAssetAdjustmentId: QualifyingAssetAdjustmentId? = null
fun assetId(v: AssetId?) = apply { assetId = v }
fun candidateAssetId(v: CandidateAssetId?) = apply { candidateAssetId = v }
fun qualifyingAssetId(v: QualifyingAssetId?) = apply { qualifyingAssetId = v }
fun qualifyingAssetAdjustmentId(v: QualifyingAssetAdjustmentId) = apply { qualifyingAssetAdjustmentId = v }
fun build() = AssetReturnValueObject(assetId, candidateAssetId, qualifyingAssetId, qualifyingAssetAdjustmentId)
}
companion object {
@JvmStatic fun builder() = Builder()
}
}
tddmonkey
02/18/2019, 5:30 PMsnowe
02/18/2019, 5:31 PMtddmonkey
02/18/2019, 5:32 PMsnowe
02/18/2019, 5:33 PMtddmonkey
02/18/2019, 5:33 PMsnowe
02/18/2019, 5:33 PMtddmonkey
02/18/2019, 5:34 PMsnowe
02/18/2019, 5:35 PMtddmonkey
02/18/2019, 5:48 PMsnowe
02/18/2019, 5:48 PMtddmonkey
02/18/2019, 5:49 PMJeff Gulbronson
02/18/2019, 7:11 PMDaniele Segato
02/18/2019, 7:49 PMgildor
02/19/2019, 2:19 AMdoes it use kapt or just a regular annotation processor?What do you mean? Annotation processors know nothing about kapt or APT, they just use jsr269 API, so it’s transparent for AP itself But if you want to use AP with Kotlin code (like in this case, because this AP works only with Kotlin code), you need Kapt, because it’s an adapter that provides jsr269 compatible API for Kotlin code and allow APs work with Kotlin in a transparent way