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

Hovering over argument with same name as outer variable produces nothing #12952

Closed
roblourens opened this issue Sep 28, 2016 · 2 comments
Closed
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues

Comments

@roblourens
Copy link
Member

From @mousetraps on September 27, 2016 21:0

Testing #12600

Using the following code and a breakpoint at the location specified location

var screenName = 'hello';

setTimeout(function() {
    console.log('done');
    a(screenName);

    process.exit();
},1000)

function a(screenName) {
    console.log(screenName); // SET BREAKPOINT HERE
}

hovering over screenName at this position should produce the string "hello", instead, no hover appears. Changing the name of the argument resolves the issue.

Copied from original issue: microsoft/vscode-node-debug2#34

@roblourens roblourens added debug Debug viewlet, configurations, breakpoints, adapter issues bug Issue identified by VS Code Team member as probable bug labels Sep 28, 2016
@roblourens
Copy link
Member Author

Hover doesn't work at that point, using either debug adapter. Seems like that's a case where it should?

@isidorn
Copy link
Contributor

isidorn commented Sep 29, 2016

There are multiple variables names screenName (in mulitple scopes). Due to the lack of language knowledge we decide to now show anything since we can not be sure over which hover the user is hovering over.
Closing as duplicate - as there are other issues like this which we plan to fix by introducing language knowledge to the hover

@isidorn isidorn closed this as completed Sep 29, 2016
@isidorn isidorn removed the bug Issue identified by VS Code Team member as probable bug label Sep 30, 2016
@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
debug Debug viewlet, configurations, breakpoints, adapter issues
Projects
None yet
Development

No branches or pull requests

2 participants