[FEATURE]: code action to fix spelling of all occurences of the symbol?

Abierto
#153 1 comentario 3 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
24/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python, rust
Área
devtools

Línea de trabajo

Start by reading the code action implementation and the discussion in issue #150; the issue does not name relevant files or tests. Check how Codebook represents spelling corrections and whether the LSP integration supports symbol rename actions. Done means a correction can offer a rename for all occurrences when another LSP provides that capability.

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

Descripción

enhancement feedback needed
Feature Description

#150 explains why Codebook typically flags only definitions - this makes a lot of sense.

Wondering then if it would be possible to have a code action that uses another LSP, if present, to rename symbol - not just change this specific spelling. No idea though if "code action calling the code action of another LSP" is technically doable, and / or if this is somehow standardized (do LSP have a standard "rename symbol" tag or name on the corresponding code action? or is it free for all?).

Use Case
def this_hhas_a_typo():
    print("typo!")

this_hhas_a_typo()

if the typo is highlighted in the def line, it would be great to provide a code action to "rename all symbol occurences"; this is typically provided by space-r in helix across programming language LSPs, so I suppose this may be somehow standardized?

Proposed Solution

If possible, have a "mirror" code action for each possible spelling correction that is "replace all symbols by ..." instead of "replace by ..."

Alternative Solutions

For now the user can get the diagnostic, decide what to use, and apply the LSP-based symbol rename themselves by typing themselves what to replace with.

Examples

No response

Additional Context

No response

Lenguaje dominante
Rust
Estrellas
925
Forks
59
Merge medio
53 min
PR fusionados (30 d)
10

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 blopker/codebook

Todos los issues de blopker/codebook

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.