Kotlin中如何将RecyclerView数据传递到DialogFragment实现删除确认

核心逻辑是通过「参数传递+回调」的方式串联ViewHolder、Dialog和宿主页面，解决跨组件无法直接访问变量的问题，完整实现步骤如下：

1. 调整FeedAdapter逻辑 #

首先修正原有适配器的语法错误，同时修改回调接口透出被点击条目的ur值：

// 把List改成MutableList方便后续删除条目更新列表
class FeedAdapter(private val posts: MutableList<FeedPost>) : RecyclerView.Adapter<FeedAdapter.ViewHolder>() { 
    // 回调改为带String参数，用于返回要删除的ur字段
    private var listener: ((deleteUr: String) -> Unit)? = null

    fun setListener(listener: ((deleteUr: String) -> Unit)?) {
        this.listener = listener
    }

    // 修正原代码中onCreateViewHolder位置错误的问题
    override fun onCreateViewHolder(parent: ViewGroup, viewType: Int): ViewHolder {
        val view = LayoutInflater.from(parent.context).inflate(R.layout.adapt_item, parent, false)
        return ViewHolder(view)
    }

    class ViewHolder(val view: View) : RecyclerView.ViewHolder(view)

    override fun onBindViewHolder(holder: ViewHolder, position: Int) {
        val post = posts[position]
        with(holder.view) {
            user_photo_image.loadUserPhoto(post.photo)
            date_text.text = post.kogda
            caption_text.setCaptionText(nachalo, post.caption)
            test.text = post.ur
            // 点击删除时把当前条目的ur传给回调
            delete_image.setOnClickListener { listener?.invoke(post.ur)  }
        }
    }

    override fun getItemCount() = posts.size

    private fun ImageView.loadUserPhoto(photoUrl: String?) {
        if (!(context as Activity).isDestroyed) {
            GlideApp.with(this).load(photoUrl).fallback(R.drawable.person).into(this)
        }
    }
}

2. 改造DeleteDialog支持参数传递与结果回调 #

给Dialog添加参数接收逻辑，拿到要删除的ur，同时添加确认回调通知宿主执行删除操作：

class DeleteDialog : DialogFragment() {
    // 定义确认删除的回调
    var onConfirmDelete: ((deleteUr: String) -> Unit)? = null

    companion object {
        // 统一的实例创建方法，通过Bundle传递参数，避免重建时参数丢失
        fun newInstance(deleteUr: String): DeleteDialog {
            val args = Bundle()
            args.putString("delete_ur", deleteUr)
            val fragment = DeleteDialog()
            fragment.arguments = args
            return fragment
        }
    }

    override fun onCreateDialog(savedInstanceState: Bundle?): Dialog {
        val view = requireActivity().layoutInflater.inflate(R.layout.dialog_delete, null)
        // 拿到传递过来的ur
        val deleteUr = requireArguments().getString("delete_ur") ?: ""
        return AlertDialog.Builder(requireContext())
            .setView(view)
            .setPositiveButton(android.R.string.ok) { _, _ ->
                // 点击确认时把ur回调给宿主
                onConfirmDelete?.invoke(deleteUr)
            }
            .setNegativeButton(android.R.string.cancel, null)
            .setTitle("Are you sure you want to delete?")
            .create()
    }
}

3. 宿主页面串联完整逻辑 #

在承载RecyclerView的Activity/Fragment中，串联点击、弹框、删除、更新列表的全流程：

// 初始化适配器时设置回调
val feedAdapter = FeedAdapter(postsList)
feedAdapter.setListener { deleteUr ->
    // 收到条目删除点击，弹出确认对话框
    val deleteDialog = DeleteDialog.newInstance(deleteUr)
    // 设置对话框确认回调
    deleteDialog.onConfirmDelete = { ur ->
        // 执行数据库删除操作
        mDatabase.child("feed-posts").child(ur).removeValue()
        // 更新列表：移除对应条目并刷新
        val deletePosition = postsList.indexOfFirst { it.ur == ur }
        if (deletePosition != -1) {
            postsList.removeAt(deletePosition)
            feedAdapter.notifyItemRemoved(deletePosition)
        }
    }
    // 显示对话框，注意传入对应FragmentManager的自定义tag
    deleteDialog.show(supportFragmentManager, "DeleteDialog")
}
recyclerView.adapter = feedAdapter

内容的提问来源于stack exchange，提问作者vad070