Skip to content

Intellisense doesn't add namespace imports #48297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
user72356 opened this issue Mar 14, 2022 · 6 comments
Closed

Intellisense doesn't add namespace imports #48297

user72356 opened this issue Mar 14, 2022 · 6 comments
Labels
Working as Intended The behavior described is the intended behavior; this is not a bug

Comments

@user72356
Copy link

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.65.2
  • OS Version: Windows 11

Steps to Reproduce:

  1. Create files test.ts and bam.ts
  2. Create and export an helloworld() function in bam.ts
  3. Type bam in test.ts and try to get VS Code to add in a namespace import in the form: import * as bam from "./bam";

I was led to believe that this was possible by the following comment: #23830 (comment)_

@mjbvz mjbvz transferred this issue from microsoft/vscode Mar 16, 2022
@mjbvz mjbvz removed their assignment Mar 16, 2022
@RyanCavanaugh RyanCavanaugh added the Working as Intended The behavior described is the intended behavior; this is not a bug label Mar 17, 2022
@RyanCavanaugh
Copy link
Member

This is the intended behavior - that comment only refers to unqualified module names, but "./bam" is a qualified path

@user72356
Copy link
Author

This is the intended behavior - that comment only refers to unqualified module names, but "./bam" is a qualified path

What's stopping Intellisense from resolving my own modules using the filename, as a code action?

@RyanCavanaugh
Copy link
Member

No one has suggested that it do so nor implemented it

@user72356
Copy link
Author

Do you see this as a worthwhile suggestion that I can make? I would take the time to submit a suggestion if there is a chance.

@RyanCavanaugh
Copy link
Member

RyanCavanaugh commented Mar 17, 2022

Sure 🙂

@typescript-bot
Copy link
Collaborator

This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Working as Intended The behavior described is the intended behavior; this is not a bug
Projects
None yet
Development

No branches or pull requests

4 participants