[FEATURE]: Improve handling of mix-case words
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Rust
- 星标
- 925
- 派生
- 59
- 平均合并
- 53 分钟
- 30 天内合并 PR
- 10
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
blopker/codebook 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 54/100
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 43/100
维护者通常 1 天内回复
-
enhancement Zed issue
难度 4/5 3-5 天 新手友好度 48/100
blopker/codebook#310 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement workaround
难度 4/5 3-5 天 新手友好度 49/100
blopker/codebook#297 · 4 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
marketing
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
polete-bermejo/floord#21 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
gbif/name-parser-rust#259 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
nledford/Ladderback#1171 ·
维护者通常 1 天内回复
-
[Bug]: LANGSMITH_SAMPLING_RATE ignores fractional values (isdigit check), traces 100% of requests未关闭
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复