Diagnostic messages need to be more friendly, more readable, and more accurate
Open
@go-wyvern is already working on this.
Since Aug 22, 2025.
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 59
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 26
Description
背景:
准确且可读的报错信息不仅有利于小朋友(开发者)发现问题,更有利于 AI 编写代码 & 修复代码。不够准确的代码诊断信息,会带来一些困扰,如:https://github.com/nighca/builder-experience/issues/32
实现路径
- 尽可能收集所有的报错信息,按来源,如类型系统,语言服务器等分类
- 按收集上来的报错信息,检查纯文字信息是否有可优化
- 类型系统定位问题的准确性,可能定位到某一行的报错,但同时夹带了其他行的报错(实际上其他行没有错误)
- 报错信息 i18n
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.