microsoft / microsoft/TypeScript
JS Doc type intellisense not working when using custom file extension
Open
Nobody has claimed this yet.
Awaiting More Feedback
Suggestion
VS Code Tracked
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
From @csvenke on September 30, 2016 20:52
- VSCode Version: 1.5.3
- OS Version: Windows 10
In a .js file, intellisense provides correct jsdoc types
In a custom extension file associated with javascript, types from jsdoc are not provided
Steps to Reproduce:
- Create a .sj file
- In settings.json, set "files.associations": { "*.sj": "javascript" }
- Create a function with jsdoc parameters with types
- Call function and check if intellisense provides types
Copied from original issue: Microsoft/vscode#13100
Contributor guide
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.
Research direction
Reproduce the issue with a .sj file, the files.associations setting in settings.json, and JSDoc-typed functions. Start by tracing how the JavaScript language service handles the associated custom extension; done means JSDoc parameter types appear in IntelliSense for .sj files as they do in .js files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100