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

Regular hover still shown when debugging #127676

Closed
alexdima opened this issue Jun 30, 2021 · 5 comments
Closed

Regular hover still shown when debugging #127676

alexdima opened this issue Jun 30, 2021 · 5 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders notebook verified Verification succeeded

Comments

@alexdima
Copy link
Member

Testing #127362

To be honest, I believe this is a VS Code core issue, but the TPI asks to create all issues here 🤷‍♂️ .

I think we normally hide the regular hover when doing debugging because of this overlap situation (cc @isidorn):

Kapture.2021-06-30.at.10.47.53.mp4
@isidorn
Copy link
Contributor

isidorn commented Jun 30, 2021

@alexdima correct, that is the motivation why we hide the regular hover (I think you even did that original code like 7 years ago :)

However note that we only hide the regular hover when we think there is a debug hover on the file (it is part of the stack frame). Code pointer

Since this is a special notebook debugging case probably some of the checks are off. I leave this to @rchiodo for an initial investigation and I can help if needed, just let me know.

@rchiodo rchiodo removed their assignment Jun 30, 2021
@rchiodo rchiodo transferred this issue from microsoft/vscode-jupyter Jun 30, 2021
@roblourens roblourens self-assigned this Jun 30, 2021
@roblourens roblourens added bug Issue identified by VS Code Team member as probable bug notebook labels Jun 30, 2021
@roblourens roblourens modified the milestones: June 2021, July 2021 Jun 30, 2021
@roblourens
Copy link
Member

roblourens commented Jun 30, 2021

@isidorn is it ok for debugEditorContribution to know about notebooks? I would make this line

if (stackFrame && this.uriIdentityService.extUri.isEqual(model.uri, stackFrame.source.uri)) {
know how to parse a notebook cell URI to compare it to the editor model URI. Or, we can have a separate notebook contrib which does basically the same thing as this method.

@isidorn
Copy link
Contributor

isidorn commented Jul 1, 2021

@roblourens that contribution has knowledge about the debug world and the editor world. So I think it is fine to add knowledge to notebooks as part of the "editor world".

@IanMatthewHuff
Copy link
Member

Looks good to me. I just the the one hover and can get the language services hover with options key.
image

@github-actions github-actions bot locked and limited conversation to collaborators Nov 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders notebook verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

6 participants
@roblourens @IanMatthewHuff @isidorn @alexdima @rchiodo and others