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 天內回覆