Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Make Traffic rows easier to read and open their messages

Abierto
  • ¿Algo no está bien?
#1,633 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
frontend, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 44 min
PR fusionados (30 d)
775

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.