-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Intellisense is not working for self-references and # imports of typescript files in vscode #57777
Comments
Probably your domain, @andrewbranch ? Or @sheetalkamat. Thank you very much for any/all help, |
Thanks @Andarist . Shouldn't the self-referencing import work already ( |
Self-references should also work. @andrewbranch has mentioned before that the code might not be best prepared for this at the moment though. I'm not sure but that might require some new preferences or considering how this would play out with the existing ones. Self-references are not that popular and might be surprising to many people. Suggesting this in import statements would be probably totally fine - but a question stays about how auto-imports should work with that. |
@Andarist I am ok using # |
I'll work on code-level improvements to my PR sometime soon. Other than that, it will require review (and merge) from the team - I can't say when that will happen. |
This issue has been marked as "Duplicate" and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
Is there any plan to support this feature in version 5.6? |
π Search Terms
"imports", "# imports"
π Version & Regression Information
β― Playground Link
https://github.com/magnusriga/my-app
π» Code
I am using
"typescript": "5.5.0-dev.20240314"
.π Actual behavior
The import specifiers do not provide Intellisense suggestions. TS is able to resolve the files however, so there is no TS error.
π Expected behavior
The expected behavior is for Intellisense to understand the TS resolution and provide suggestions with ctrl+space.
Additional information about the issue
No response
The text was updated successfully, but these errors were encountered: