-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
lsp: not resolving extending interfaces with import map #10439
lsp: not resolving extending interfaces with import map #10439
Comments
Can you provide how you are importing |
I use an import_map.json but it's a local file imported like this @kitsonk |
And I assume It should work, I am not sure why it isn't... could be something to do with how the language server is handling the import map internally. |
I commented out I'm on windows 10 if that makes a difference |
@kitsonk I've figured out how to trigger it. An import map works for local files (like in the first image below) but external modules need to load from it's URL or else you get the error above on load. So below works on-load if I use |
@kitsonk Here's another use case with purely local modules that triggers the same when extending an interface. Using import map and And if I enter the file |
There seem to be an issue with extending interfaces not resolving sometimes.
I open my workplace in vscode and enter file
![image](https://user-images.githubusercontent.com/11677530/115927725-28f9d780-a485-11eb-96b7-809d201e5f12.png)
a.ts
and it doesn't detect the interface extendingContext
fromoak
But when just 'entering' the file which returns the interface that extends
![image](https://user-images.githubusercontent.com/11677530/115931778-0919e200-a48c-11eb-8702-b1cbe905c1c7.png)
Context
. It gets resolvedAnd it now works if I tab back to
![image](https://user-images.githubusercontent.com/11677530/115931655-ce17ae80-a48b-11eb-9ad5-2669bb3e8d36.png)
a.ts
If this is not a bug, I'd appreciate any pointer on how to 'load' all files in a workplace to resolve the intellisense at startup
.vscode/settings.json
vscode: 1.55.2
deno: 1.9.2
extension: 3.3.0
Thanks
The text was updated successfully, but these errors were encountered: