[FEATURE]: Enhancements to align the VS Code extension with ecosystem covention
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
Línea de trabajo
The issue proposes four separate VS Code extension changes: command palette actions, bundling the codebook-lsp binary, syncing dictionary settings, and lowering VS Code version requirements. Start by reading the extension's package configuration and implementation to map each proposal to its entry points. Done means agreeing on scope and completing the selected change with suitable coverage; the issue does not specify files or tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Feature Description
Hello @blopker ,
First, thank you for creating codebook! As a VS Code user for years, I've used CSpell Checker as my first choice, but I grew tired of its insensible memory consumption (often 300~500MB for a single file). Finally, I found this project provides similar features but with less source consumption. I'm a big fan now and excited about its potential.
As for VS Code extension, it's clear that it is in a very early stage and has many aspects to improve. So I'm opening this issue to propose a series of enhancements that would align it more closely with VS Code's ecosystem conventions and improve the overall user experience. I understand some conventions are quite different from other editors, so some of them may be quite tricky to handle.
I believe these changes would make codebook even more attractive to VS Code users and help get the extension ready for publishing. I'm happy to discuss them and would be willing to contribute pull requests to implement them incrementally.
Use Case
-
Code actions: Although VS Code has great support for code actions of LSP, using them frequently (for operations like "Add word to dictionary") can introduce some friction.
-
Binary distribution: Unlike other editors, the convention for VS Code extensions that rely on a binary is to bundle the executable within the .vsix file. This is because several reason:
- The Microsoft marketplace holds do not restrict the package size of extension, and it's accessibility in certain country and regions is better than Github.
- Downloading the binary during editor startup often hits the limitation of anonymous rate, which exert negative influence to user experience.
- VS Code allows user to pin extension versions. If the extension is not self-contained this may not work as expected. For example, I once had to pin
rust-analyzerto an older version because a newer release maxed out my CPU
-
Dictionary synchronization: The extension stores the user dictionary in
~/.config/codebook/. While this is great for cross-editor consistency, it bypasses VS Code's native settings sync feature, which many users rely on to sync their entire editor environment across devices. -
VS Code compatibility: In commit 9b83dd9e4bcb39bc23d510baee08c622c96dd86a , the
engines.vscodewas set to^1.109.0. This will prevent users who is not using the latest VS Code from using this useful extension, which I guess was not original intention.
Proposed Solution
-
Code actions: I propose following CSpell's convention by adding quick commands to command palette. For example, we can register commands like "Add word to dictionary" in the LSP client, which simply trigger the corresponding command of LSP server. This does not require many changed on
codebook-lspitself. -
Binary distribution: Since many other popular extension bundle binary files (such as ruff, rust-analyzer and Microsoft's cpp tools), I proposed packaging the
codebook-lspexecutable to VS Code extension and aligning their versions. This does not require major changes as they are currently share the same github repository. Besides, for user who has installedcodebook-lspglobally, we can detect it and use global installed one previously. -
Dictionary synchronization: Since CSpell Checker has provided a extension settings field
cSpell.userWordsinsettings.json, it will be helpful to have a similar filed in the codebook extension and has a merge logic to combine editor settings with global settings fill. This would support syncing the dictionary across different devices while maintaining cross-editor consistency on a single device. -
VS Code compatibility: Considering that VS Code has no massive changes recently (despite copilot), I suggest rolling back the
engines.vscodeto^1.80.0. We should also pin@types/vscodeto the same version, as it corresponds to the engine version. And just ignore it during update.
Alternative Solutions
No response
Examples
No response
Additional Context
These are quite a lot changes and may take some time to implement. As I have experience in VS Code extension development, I would love to contribute and submit PRs for these. Please let me know what you think!
- Lenguaje dominante
- Rust
- Estrellas
- 925
- Forks
- 59
- Merge medio
- 53 min
- PR fusionados (30 d)
- 10
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin 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 blopker/codebook
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 54/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 43/100
Los mantenedores suelen responder en 1 día
-
enhancement Zed issue
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
blopker/codebook#310 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[FEATURE]: Per-language `words`Abiertoenhancement workaround
Dificultad 4/5 3-5 días Aptitud para principiantes 49/100
blopker/codebook#297 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de blopker/codebook
Issues similares
-
marketing
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
polete-bermejo/floord#21 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
gbif/name-parser-rust#259 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
nledford/Ladderback#1171 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: LANGSMITH_SAMPLING_RATE ignores fractional values (isdigit check), traces 100% of requestsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día