microsoft / microsoft/TypeScript
checkJs: x.js should use x.d.ts for type inference
未关闭
还没有人认领这个 Issue。
Awaiting More Feedback
Suggestion
- 主要语言
- Go
- 星标
- 111k
- 派生
- 14.4k
- 平均合并
- 1 天 19 小时
- 30 天内合并 PR
- 117
描述
Suggestion
🔍 Search Terms
checkjs, declaration files
✅ Viability Checklist
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- This feature would agree with the rest of TypeScript's Design Goals.
⭐ Suggestion
If a declaration file with the same name than a JavaScript file is available (in the same location), then the declaration file should be used to check the js file.
📃 Motivating Example
Assume that "checkJs" and "strict" options are enabled.
Given the following files:
// @filename a.d.ts
export function f(n: number): number;
// @filename a.js
function f(a) {
// Parameter 'a' implicitly has an 'any' type
return a + 1
}
the type of f should be inferred and should thus type-check. TSC does not currently use a.d.ts to infer types of a.js.
Note that importing f in another js file, already infer f's type
// @filename b.js
import { f } from "./a.js"
// type of f is inferred
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
先使用 a.d.ts、a.js 和 b.js 创建 checkJs 和 strict reproducer,然后对其运行 TypeScript 的 checker,以确认当前的诊断结果。跟踪如何为导入的 f 解析声明文件,并将其与直接检查 a.js 的结果进行比较。当 a.js 的类型检查使用同名声明且不改变生成的 JavaScript 时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, typescript
- 领域
- compilers
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100