microsoft / microsoft/TypeScript
feature request: public the TransformationContext.addDiagnostic and read them in the compiler and transpileModule
还没有人认领这个 Issue。
- 主要语言
- Go
- 星标
- 111k
- 派生
- 14.3k
- 平均合并
- 1 天 19 小时
- 30 天内合并 PR
- 117
描述
Search Terms
custom transformer diagnostic
Suggestion
mark the method addDiagnostic in TransformationContext as public and read the diagnostic result in the compiler
Use Cases
I'm writing a custom transformer. In some cases, the transform will fail but I don't want to throw an Error. I want to add my error to the diagnostics.
Examples
I have tried to call the addDiagnostic by as any
function createDiagnosticForNodeInSourceFile(
ts: ts,
sourceFile: SourceFile,
node: Node,
message: DiagnosticMessage,
arg0?: string | number,
arg1?: string | number,
arg2?: string | number,
arg3?: string | number,
): DiagnosticWithLocation | undefined {
return (ts as any).createDiagnosticForNodeInSourceFile?.(sourceFile, node, message, arg0, arg1, arg2, arg3)
}
function appendDiagnosticMessageForNode(context: TransformationContext, diag: DiagnosticWithLocation | undefined) {
if (!diag) return false
const _context = internalTransformationContext(context)
if (!_context.addDiagnostic) return false
_context.addDiagnostic(diag)
return true
function internalTransformationContext(
context: TransformationContext,
): TransformationContext & { addDiagnostic?(diag: DiagnosticWithLocation): void } {
return context as any
}
}
But that doesn't work. After digging into the source code, I found that it seems like the diagnostics only read in the dts generating.
Checklist
My suggestion meets these guidelines:
- 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, etc.)
- This feature would agree with the rest of TypeScript's Design Goals.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先,沿着 issue 中提到的 compiler、transpileModule 和声明生成路径跟踪 TransformationContext.addDiagnostic。确认当前在哪里读取 transformer diagnostics,然后确定所需的测试,以证明 custom transformer 添加的 diagnostic 会进入 compiler 和 transpileModule 的结果。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- typescript
- 领域
- compilers
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100