在 Kotlin 的 Data 类中拥有内部类和接口是否是最佳实践

Question

我有一个数据类，它是一个房间实体，代码如下

@Entity(tableName = "request")
data class Request(
@PrimaryKey
var id: Int,
var name: String,
var date: String,
var requestTime: String,
var deliveryTime: String,
var distanceCovered: String
){
interface OnClickListener{
    fun onClick(request: Request)
}

class Adapter(
    private val requests: List<Request>,
    private val requestsFor: Int,
    private val listener: Request.OnClickListener
) : RecyclerView.Adapter<Adapter.ViewHolder>() {

    companion object{
        const val REQUESTS_FOR_SEND = 0
        const val REQUESTS_FOR_ONGOING = 1
        const val REQUESTS_FOR_COMPLETED = 2
    }

    class ViewHolder(
        var recyclerViewRequestBinding: RequestBinding
    ) : RecyclerView.ViewHolder(recyclerViewRequestBinding.root)

    override fun onCreateViewHolder(parent: ViewGroup, viewType: Int) =
        ViewHolder(
            DataBindingUtil.inflate(
                LayoutInflater.from(parent.context),
                R.layout.request,
                parent,
                false
            )
        )

    override fun getItemCount() = requests.size

    override fun onBindViewHolder(holder: ViewHolder, position: Int) {
        val request = requests[position]
        holder.recyclerViewRequestBinding.request = request
        when(requestsFor){
            REQUESTS_FOR_COMPLETED ->{
                holder.itemView.request_date.hide()
                holder.itemView.request_delivery_time.show()
                holder.itemView.request_distance_covered.show()
            }
        }
        holder.itemView.setOnClickListener { listener.onClick(requests[position]) }
    }
}
}

在这里你可以看到Request 是一个Room 实体，它有它的内部类Adapter 和接口OnClickListener 在实体中包含这些东西是一个好习惯，如果这是一个坏习惯那么最佳做法是什么？

Answer 1

根据SOLID 规则，每个类都应该有单一的职责。您可以将 ViewHolder 设为 Your Adapter 的内部类。接口和实体应该分开。