microsoft / microsoft/TypeScript
Customise extensions that import intellisense recognises
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
From @Rich-Harris on October 6, 2017 15:7
As of VSCode 1.17, typing import x from './ offers autocomplete suggestions of local files and directories. However, the list of file extensions that are recognised is somewhat arbitrary — .js files are recognised, as are .ts and .jsx, but .json isn't (despite the fact that the Node handles .json files natively).
Meanwhile, when building web applications with bundlers like Webpack and Rollup, it's common to import files with extensions like .css, .html, .vue, .tsv and so on.
Is there some way to customise the list of extensions that are recognised? An alternative approach could be to recognise all file extensions rather than attempting to filter them.
Copied from original issue: Microsoft/vscode#35731
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
No files or tests are named. Start by locating the VSCode import-completion logic described in the issue and check how recognized extensions are defined; done means the extension list can be customised or the requested broader recognition behavior is implemented and covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100