microsoft / microsoft/java-debug
References to launch.json in error messaging may be misleading
还没有人认领这个 Issue。
- 主要语言
- Java
- 星标
- 409
- 派生
- 204
- 平均合并
- 1 天 13 小时
- 30 天内合并 PR
- 4
描述
https://github.com/microsoft/java-debug/search?q=launch.json
There appear to be only two references to launch.json in this repository. There does not appear to be any part of the code actually reading or referencing or introspecting a file named launch.json.
End users may find references to launch.json confusing if a third party tool has launched the debugger to connect to a java process and did not pass in a "projectName" to the call. While I realize this is a bit outside the scope of this repository, an example would be a vscode extension using the vscode.debug API (which flows to the https://github.com/microsoft/vscode-java-debug extension) and not setting a project name. In this case there is no launch.json file.
private async startDebugger(port: string) {
this.port = port;
vscode.debug.startDebugging(undefined, {
type: 'java',
request: 'attach',
name: 'Debug (Remote)',
hostName: 'localhost',
port,
projectName // set to undefined as an example
});
}
Since this repository itself does not read a launch.json at all, and all configuration is passed in via a Debug Adapter, not an existing file, these references to a file name are very misleading.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 issue 中链接的 launch.json 仓库搜索开始,并检查两个错误消息引用。确定不会暗示此仓库读取 launch.json 文件的措辞;对于通过 VS Code debug API 启动的调试器会话,当这些容易误导的引用得到澄清或移除后,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java, vscode
- 领域
- devtools
- Issue 类型
- 缺陷
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100