Make Traffic rows easier to read and open their messages
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The issue names no files or tests; first locate the Traffic row implementation, its navigation entry points, date-rendering code, and reminder labels. Run the existing manager/member workflow and inspect current date fixtures, then cover the listed navigation, visibility, responsive, timestamp, and separator acceptance cases.
由索引模型根据 Issue 内容生成。
描述
Problem
Traffic rows should show how old a message is and let the person open that message by pressing the row. The sender handle and thread disclosure must keep their separate actions. Older rows should retain short relative ages rather than switching to a calendar date. Related reminder labels should use the same middle-dot separator consistently.
This tracks the narrow changes proposed in #1500 and #1503, independently of their older team-feature branch history.
Acceptance
- In a real manager/member workflow, pressing a Traffic row opens its owning conversation at the associated message. Pressing a handle opens that member, while pressing the disclosure opens the thread. Same-conversation navigation works too.
- Navigation reveals the target when its activity group is collapsed; it does not silently land on an invisible message.
- Narrow layouts preserve sender, recipient and thread controls; message wording yields space to a compact age. Missing timestamps render nothing.
- Deterministic date fixtures cover minutes, hours, days, weeks and years, including boundaries and future timestamps. A live workflow verifies current ages and resizing.
- One-time reminder wording and its approval label use the middle dot consistently. Record the actual terminal workflow and independently use its resulting artifact.
Related but separate: #1524 concerns missing Traffic events, and #1552 concerns Teams keyboard focus. This issue does not claim to resolve either.
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 9 小时 44 分钟
- 30 天内合并 PR
- 766
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Agent-Field/CodeAF 的其他 Issue
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 86/100
Agent-Field/CodeAF#1592 ·
维护者通常 1 天内回复
-
area:headless bug sev:critical
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1566 · 已指派 1 人 ·
维护者通常 1 天内回复
-
area:chat feature
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1510 ·
维护者通常 1 天内回复
-
area:tests bug
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1489 ·
维护者通常 1 天内回复
-
area:chat bug good first issue sev:papercut
难度 2/5 1-3 小时 新手友好度 78/100
Agent-Field/CodeAF#1470 ·
维护者通常 1 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
automation models
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
txn2/mcp-data-platform#1984 ·
维护者通常 1 天内回复
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
kind/docs prio/P2
难度 1/5 1 小时以内 新手友好度 95/100
agent-substrate/substrate#1986 ·
维护者通常 1 天内回复