Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Make Traffic rows easier to read and open their messages

Aberta
  • Algo errado?
#1,633 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
frontend, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
115
Forks
14
Merge médio
9h 44min
PRs com merge (30d)
766

Preparar o ambiente

Ainda não verificamos os arquivos de configuração deste projeto. Comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Agent-Field/CodeAF

Todas as issues de Agent-Field/CodeAF

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.