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

Add LSP diagnostics to completion requests

Abierto
  • ¿Algo no está bien?
#448 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
clojure
Área
tooling

Línea de trabajo

The issue does not identify ECA files, tests, or entry points; first locate how completion requests are assembled and where LSP data is available. Resolve the open questions about which diagnostics to include, scope, and configurability before implementation; done means completion requests carry the agreed diagnostic context, with tests covering the chosen behavior.

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

Descripción

To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.

Completion (aka next edit prediction, ai autocomplete, ai tab complete, etc) would benefit from LSP diagnostics.

Prior Art
Cursor

Info pulled from minified JS via an Agent. Take with a grain of salt.

Example JSON

The following JSON snippet is an example payload based on the keys in the bundle. This unfortunately was not logged or pulled from a running application.

{
  "linterErrors": {
    "relativeWorkspacePath": "src/parser.rs",
    "errors": [
      {
        "message": "expected `;`, found `}`",
        "source": "rustc",
        "uri": "file:///project/src/parser.rs",
        "severity": "ERROR",
        "range": {
          "startPosition": { "line": 42, "column": 5 },
          "endPosition": { "line": 42, "column": 6 }
        },
        "relatedInformation": []
      }
    ]
  },
  "lspSuggestedItems": { "suggestions": [{ "label": "parse_expr" }] },
  "parameterHints": [
    {
      "label": "fn read(path: &Path) -> Result<String, Error>",
      "documentation": "Reads the entire file into a string."
    }
  ],
  "lspContexts": []
}

(Real requests include many non-LSP fields: currentFile, diff histories, workspaceId, codeResults, timing, etc.)

Scope
  • linterErrors is for the current file only.
  • additionalFiles (visible-range snippets, paths, open files, recently viewed, etc.) can include other buffers when enableRvfTracking is enabled.
Zed

Zed is open source! Much easier to read. Zed sends LSP context in the user prompt. It looks like LSP diagnostics get serialized to a token friendly format and embedded into the prompt.

Link to Diagnostic type def
Link to collect_diagnostics
Link to user prompt type def

Zed also sends related_files from go to definition (from users cursor) and type defintions.

Outstanding Questions
  • What LSP info should be included in the completion request
    • Should the selected diagnostics be configurable in ECA config?
  • Would any other request types benefit from LSP information?
  • Should diagnostics be limited to the file being editted or should it include full workspace diagnostics?
    • It looks like Cursor and zed both support this but have booleans to enable. There is probably a reason for the boolean. May be good to test.
Lenguaje dominante
Clojure
Estrellas
1k
Forks
82
Merge medio
3 d 39 min
PR fusionados (30 d)
15

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 editor-code-assistant/eca

Todos los issues de editor-code-assistant/eca

Issues similares

Más issues de Clojure

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.