microsoft / microsoft/TypeScript
Add JSDOC @module support for intellisense.
还没有人认领这个 Issue。
- 主要语言
- Go
- 星标
- 111k
- 派生
- 14.3k
- 平均合并
- 2 天 4 小时
- 30 天内合并 PR
- 132
描述
Search Terms
Intellisense jsdoc support for modules
Suggestion
When adding /** @module moduleName Module Description. */ to a module, then doing this:
import * as myName from "./moduleName";
I think it makes sense, when importing the whole namespace, to include the jsdoc @module comment.
I also think that when pressing Ctrl+Space for code completion on "./" (to get a list of modules) should also show the module documentation.
Use Cases
Better support for module documentation. I'm developing some module libraries and it would be great to give end users a good experience with better intellisense documentation.
Examples
aModule.ts
`/** @module aModule Does something awesome. */`
app.ts
import * as aModule from "./aModule";
// (moduleName should both have the doc details)
// ("./{*.*}" - all files in code completion should show the documentation as well)
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 编号。
调研方向
复现 aModule.ts 和 app.ts 中的示例,然后检查现有的 JSDoc,以及命名空间导入和 "./" 补全的模块补全行为。完成标准是:@module 文档会显示在已导入的命名空间上,并显示在模块建议旁边,同时不改变运行时输出。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, typescript
- 领域
- developer-experience, tooling
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100