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

wip: improve search highlight experience

Abierto
  • ¿Algo no está bien?
#1,000 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git, typescript
Área
developer-experience, search

Línea de trabajo

Start by reading the existing diff and context-plugin code, then inspect how whiteboard’s data model represents regions and evidence; the issue does not name specific files or tests. The proposal spans a new diffr search command, diff caching, and whiteboard integration, so clarify the interface and scope before taking it on. Done means highlighted regions can be surfaced in code peeks and diff lenses, with the surrounding diff folded appropriately.

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

Descripción

We need support for actual highlights within regions in both code peeks + diff lenses. Example - you might imagine that the model may only want to show you lines 22-28 of this, but you're forced to see the whole thing:

Image

In the sense that a model is going to select a region of code to show you - it may not be the entire diff. But showing only those lines is sad because you lose context for the surrounding code (which is sad as you start to get a feeling for the system).

A tentative approach:

  • a 'diffr search' subcommand that:

    • takes in 'git grep' shaped input (commit:fileName:lineNo: text)
    • joins that with diffr-computed diffs
    • runs the context plugin to only show the region highlighted (within the context of the larger diff)
    • i'd imagine you'd only want to show the highlighted region at first, but should treat e.g. a highlighted region within a changed region as ok.

  • some wiring into whiteboard so that the data model accepts this

    • i think the mcp structure for "give me a region to show within a diff" is also a bit weird.
    • right now the model needs to give you precise line numbers etc.
    • instead, you could imagine the model could run:
      git grep <pattern> | diffr search and pipe that into whiteboard as evidence
      • diffr search returns a list of hits (so we can work in a decision model somehow)

  • other notes: computing diffs is expensive / slow. so i thought we could read cached diffs from .cache/diffr or something like that (the XDG standard or whatever)

  • internally, i broke up search into 'hydrate' -> 'postprocess' to resemble a normal search pipeline. this would let us insert e.g. jev/openai decisions at parts in the pipeline to filter results if we wanted to !

Lenguaje dominante
TypeScript
Estrellas
2.9k
Forks
145
Merge medio
16 h 28 min
PR fusionados (30 d)
553

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: 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 devdotfast/whiteboard

Todos los issues de devdotfast/whiteboard

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.