hub-client: keep resolved comments visible

未关闭
#976 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
frontend

调研方向

The payload does not name files or tests. Start by locating the hub-client comment resolution and rendering entry points, then read the related issues #642 and #953 for context. Done means resolved comments remain visible in a de-emphasized state, can be expanded, and can be reopened.

由索引模型根据 Issue 内容生成。

描述

Summary

Resolving a comment (the checkmark) removes it entirely. Other collaborators can't see the comment, its replies, or that it was resolved.

Request

Keep resolved comments visible in a de-emphasized state, for example collapsed or grayed out, with a way to expand and reopen them.

Impact

In a review, the author resolves comments as they address them. Once a comment disappears, the reviewer can't confirm their point was handled or see how it was answered, and the discussion is lost for anyone reading the doc later.

Related
  • #642 (resolving leaves a visual halo in the block editor)
  • #953 (undoing a resolve should be trivial). Visible resolved comments would make undo straightforward.
主要语言
Rust
星标
293
派生
20
平均合并
12 小时 30 分钟
30 天内合并 PR
175

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

quarto-dev/q2 的其他 Issue

查看 quarto-dev/q2 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。