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

Replace file-reference chip path display

Abierto
#509 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
css, typescript
Área
frontend

Línea de trabajo

Start in src/features/messages/components/Markdown.tsx by reading FileReferenceLink, relativeDisplayPath, and parseFileReference, then inspect the .message-file-link-* rules in src/styles/messages.css. Ensure chips never display ../, duplicate basenames remain readable, full paths stay available through the existing access points, and opening files is unchanged.

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

Descripción

In chat message bubbles, file references are rendered as a “chip” (.message-file-link) showing a blue basename plus a grey “parent path”. When the referenced path is outside the workspace root, that grey portion becomes a long workspace-relative path full of ../ segments (e.g. ../../../../config/...).

Problems

  • The ../-heavy relative path is hard to read/scan and often looks like part of the value/code.
  • It does not help disambiguate files that share the same basename across different folders, because the displayed path is effectively unreadable.
  • When basenames collide, the suffix path still doesn’t help because it’s a noisy wall of ../ segments; it’s hard to understand which folder a file is actually in.
  • The ordering (basename first, then parent path) is confusing; the suffix doesn’t read like a normal breadcrumb/path.

Request

  • Don’t show ../ segments in the UI for file-reference chips.
  • Either:
    1. Hide the grey parent-path suffix entirely (keep full path in tooltip/context menu), OR
    2. Replace it with a readable disambiguation path (e.g. trailing segments like …/parent/file.ext or parent/file.ext) that never includes ../, and expands as needed when basenames collide.

Acceptance criteria

  • No file-reference chip ever displays ../.
  • Duplicate basenames remain distinguishable (or we fall back to a more readable truncated path).
  • Full path is still accessible (tooltip/context menu) and open-file behavior is unchanged.

Implementation pointers

  • FileReferenceLink + relativeDisplayPath / parseFileReference in src/features/messages/components/Markdown.tsx
  • Styling in src/styles/messages.css (.message-file-link-*).
Lenguaje dominante
TypeScript
Estrellas
4.3k
Forks
416
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 Dimillian/CodexMonitor

Todos los issues de Dimillian/CodexMonitor

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.