Skip to content
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

Go to Definiton does not work in JavaScript namespace #27045

Closed
StaticNoiseLog opened this issue May 22, 2017 · 1 comment
Closed

Go to Definiton does not work in JavaScript namespace #27045

StaticNoiseLog opened this issue May 22, 2017 · 1 comment
Assignees
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@StaticNoiseLog
Copy link

  • VSCode Version: Code 1.12.2 (19222cd, 2017-05-10T13:20:36.315Z)
  • OS Version: Windows_NT ia32 10.0.15063
  • Extensions:
Extension Author Version
vscode-eslint dbaeumer 1.2.11
vscode-firefox-debug hbenl 0.13.1
debugger-for-chrome msjsdiag 3.1.1
unity-debug Unity 1.2.0

Steps to Reproduce:

  1. Create a JavaScript File with this content (the variable c99 is used to wrap the Game class in its own namespace, a common pattern in JavaScript):
var c99 = {};

c99.Game = (function () {
    function Count99Game() {
        console.log('Count99 game starts.');
        this.initGame();
    }

    Count99Game.prototype.initGame = function () {
        this.nextCountLabel = document.getElementById('next-count');
    };

    return Count99Game;
})();
  1. Right-click on the "initGame" function on line 6 and choose "Go to Definition". Nothing happens. Expected behavior: The cursor should be positioned on line 9 where the function is defined. Works in NetBeans, for example.
@mjbvz
Copy link
Collaborator

mjbvz commented May 22, 2017

This issue was moved to microsoft/TypeScript#15996

@mjbvz mjbvz closed this as completed May 22, 2017
@mjbvz mjbvz added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label May 22, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants