feat(ui): show the definition of each row for a name with several definitions
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
- 35/100
Línea de trabajo
Start in internal/uiserver/handlers.go, where the UI calls Callers, Callees and Impact, and in the uiv1.Location protobuf message, which needs a definition-label field. Read decision D8 in the archived change and the same-name-query-targets change (#318), which this depends on, before touching the response shapes. Done when each row carries its definition label, the three responses carry the definition list, the three requests accept a file input matching --file, and the Svelte views display both, with single-definition names unchanged.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What exists today?
The graph UI calls the engine functions Callers, Callees and Impact through internal/uiserver/handlers.go. Each row is a uiv1.Location with a name, a kind, a file and a line.
How does it behave now?
The change same-name-query-targets (#318) makes those functions answer for every definition of a name. The CLI and the MCP tools then name the definition of each row and list the definitions. The UI gets the same rows, but uiv1.Location has no field for the definition, and the responses have no list of definitions. A UI row for a name with several definitions shows its own file and line. It does not show which definition it belongs to.
The UI requests also have no file input, so the UI has no way to select the definitions in one file.
How should it behave?
uiv1.Locationcarries the definition label of the row.- The callers, callees and impact responses carry the list of definitions.
- The three requests accept a file, with the meaning of
--file. - The Svelte views show the label and the list.
The design of the archived change records this cut in its decision D8.
What kind of improvement?
Other
Would this change existing behavior?
The protobuf messages gain fields, which is additive. The views show more text for a name with several definitions. A name with one definition looks the same.
Before submitting
- I searched existing issues and this is not a duplicate
- I checked that the current behavior is not a deliberate decision in
openspec/specs/
- Lenguaje dominante
- Go
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 7 h 42 min
- PR fusionados (30 d)
- 111
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de seanb4t/codegraph-go
-
chore needs-triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
seanb4t/codegraph-go#380 ·
Los mantenedores suelen responder en 1 día
-
chore needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
seanb4t/codegraph-go#379 ·
Los mantenedores suelen responder en 1 día
-
area:query chore needs-triage spec-needed
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
seanb4t/codegraph-go#377 ·
Los mantenedores suelen responder en 1 día
-
chore needs-triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
seanb4t/codegraph-go#362 ·
Los mantenedores suelen responder en 1 día
-
area:query bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
seanb4t/codegraph-go#355 ·
Los mantenedores suelen responder en 1 día
Todos los issues de seanb4t/codegraph-go
Issues similares
-
Add iterate GmbH domains to a dedicated list and include it in company and developer categoriesAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
v2fly/domain-list-community#4307 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
notify: voice_queue rows are deleted only at startup, so a hub that stays up grows it without boundAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
mattabate/life-distributable#232 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día