feat(ui): opt-in whole-symbol graph inside a drilled-into package

Abierto
#117 0 comentarios 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, react
Área
cli, devtools

Línea de trabajo

The request is for an opt-in, package-scoped symbol graph in the graph view, and the payload gives no file or entry point to start from. Begin by reading the planning files linked in the body (GRF-07 in .planning/ROADMAP.md and v0.13.0-REQUIREMENTS.md line 78) to learn the render-time threshold protocol. Done means a threshold commit exists first and a guava measurement passes it, which is measurement and design work rather than a first edit.

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

Descripción

area:ui feature priority:low spec-needed
What problem does this solve?

The graph view stops at files and packages. A user who drills into a package cannot see the symbol-level call structure inside it.

What should it do?

An opt-in symbol graph scoped to one package that is already drilled into. Commit the render-time threshold first, before any measurement (the GRF-01/GRF-09 protocol).

Which surface does this affect?

Other (UI)

Is this covered by an existing command or tool today?

callers/callees/impact give lists, not a graph. v0.12.0 Phase 5 measured that a 3,233-node file view never converged on guava, so the budget must be set and measured before building.

Acceptance criteria
  • A committed threshold, then a measurement on guava that passes it, with the threshold commit as an ancestor of the measurement.

Source (GSD planning files, archived at d384473e): .planning/ROADMAP.md (Later: GRF-07); .planning/milestones/v0.13.0-REQUIREMENTS.md:78


🤖 Generated with Claude Code

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

Lenguaje dominante
Go
Estrellas
0
Forks
0
Merge medio
7 h 42 min
PR fusionados (30 d)
111

Preparar el entorno

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 seanb4t/codegraph-go

Todos los issues de seanb4t/codegraph-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.