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.

Sign up for GitHub

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

Jump to bottom

Debug hover could trigger a lazy variable refresh #143725

Closed
weinand opened this issue Feb 23, 2022 · 4 comments
Closed

Debug hover could trigger a lazy variable refresh #143725

weinand opened this issue Feb 23, 2022 · 4 comments
Assignees
@roblourens
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *out-of-scope Posted issue is not in scope of VS Code

Comments

@weinand
Copy link
Contributor

weinand commented Feb 23, 2022 •
edited
Loading

Testing #143572

  • hover over a lazy variable to trigger a fetch of the value

Observe: hover shows real value but Variables view or inline values do not

CleanShot 2022-02-23 at 14 40 17

This behavior is different from the Variables view where fetching a "lazy" value triggers an inline values update.
@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Feb 23, 2022
@roblourens
Copy link
Member

I am not sure that it can know that an evaluated expression corresponds to a certain variable, but I can look into it

@weinand
Copy link
Contributor Author

weinand commented Feb 23, 2022 •
edited
Loading

@roblourens this is not an important issue, more a "nice to have"...
I only noticed it because the Variables view triggers a refresh of "inline values"...

@roblourens roblourens added the bug Issue identified by VS Code Team member as probable bug label Feb 23, 2022
@roblourens roblourens added this to the Backlog milestone Feb 23, 2022
@roblourens
Copy link
Member

I don't want to try to tie the hover expression to something in the variables view, it's complicated and can't be done perfectly.

@roblourens roblourens removed this from the Backlog milestone Apr 15, 2022
@roblourens roblourens added the *out-of-scope Posted issue is not in scope of VS Code label Apr 15, 2022
@weinand
Copy link
Contributor Author

weinand commented Apr 19, 2022

@roblourens makes sense. I support your decision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@roblourens roblourens

Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roblourens @weinand