[FEATURE]: Improve handling of mix-case words
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Facilidade para iniciantes
- 57/100
Direção de pesquisa
The issue points to crates/codebook/src/splitter.rs around lines 46–47. Read the splitter and trace how its configuration is defined and used, then check the related tests. Done looks like mixed-case words such as “PostgreSQL” are handled according to a configurable case-splitting choice without breaking existing behavior.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Feature Description
Hi! Thanks for a great bit of software, I've dropped nvim's built-in spellcheck due to issues with tree-sitter and I'm really liking using codebook-lsp instead!
That said, I've noticed that mixed-case words, such as "PostgreSQL", don't quite work as I would expect. This seems to be because the splitter code here is splitting on case changes.
It would be really great if there was a way to enable/disable case-based splitting to account for proper nouns such as "PostgreSQL" — a word that codebook knows about out-of-the-box!
I am not filing this is a bug because I don't think it's something not working as intended per-se, but you might prefer that it is one? Please let me know.
Use Case
In my case I have comments/docs that refer to PostgreSQL, and codebook detects that "Postgre" is not a word it knows, and helpfully offers to replace it with PostgreSQL, which then makes the word PostgreSQLSQL 😂 Which is, of course, still flagged as a mis-spelling.
Proposed Solution
The simplest solution is a config-driven toggle, to control whether the splitter splits on case boundaries at all?
Alternative Solutions
A more complicated solution would be to have the splitter return the whole word as the first potential split for case based splits (not just the individual parts), and if that happens (and is a valid word), then it could ignore the subsequent split elements?
Examples
This is an example of the problem, and what I'd like to see instead
https://github.com/user-attachments/assets/0a61c7f4-91de-47fd-8bde-22e2601186cd
Additional Context
I am not really a rust dev, so I might have missed something very obvious when reading the code. That said, I am happy to try my hand at writing some rust for this as a PoC, if you'd want to see the code explored at least a little bit first.
- Linguagem predominante
- Rust
- Estrelas
- 925
- Forks
- 59
- Merge médio
- 53min
- PRs com merge (30d)
- 10
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de blopker/codebook
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 54/100
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 43/100
Mantenedores costumam responder em até 1 dia
-
enhancement Zed issue
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 48/100
blopker/codebook#310 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
enhancement workaround
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 49/100
blopker/codebook#297 · 4 comentários ·
Mantenedores costumam responder em até 1 dia
Todas as issues de blopker/codebook
Issues semelhantes
-
marketing
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
polete-bermejo/floord#21 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
gbif/name-parser-rust#259 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
nledford/Ladderback#1171 ·
Mantenedores costumam responder em até 1 dia
-
[Bug]: LANGSMITH_SAMPLING_RATE ignores fractional values (isdigit check), traces 100% of requestsAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
Mantenedores costumam responder em até 1 dia