-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
can't navigate javascript with manual namespaces #7632
Comments
From @chadbr on March 22, 2016 0:21 oh - and FWIW, WebStorm allows me to navigate these files... |
This is a major road block for our team to adapt VSCode and TypeScript because our main product is still using global namespace (due to ExtJS). |
I'm assuming this won't be supported any time soon (if ever...) |
This seems easily as reasonable as tracking prototype assignments. |
Any news? It's very annoying that by simply namespacing objects you no longer get IntelliSense. |
Another pattern referenced in microsoft/vscode#27246 is |
If https://github.com/tc39/proposal-nullish-coalescing advances, you may want to revisit this issue. |
From @chadbr on March 22, 2016 0:18
I have large legacy codebase with "manual" style namespacing like this:
and "classes" declared like this:
my.app.Application` = (function () {
var Application = function () {
...
};
return Application;
})();
I've tried several combinations of jsconfig.json parameters and none allow me to navigate this style of code. Should this work?
Steps to Reproduce:
vscodeTestJS.zip
Copied from original issue: microsoft/vscode#4533
The text was updated successfully, but these errors were encountered: