Skip to content

Variables should reflect changes made by the user in the debug console #58

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

Open
rkeithhill opened this issue Dec 3, 2015 · 9 comments
Labels
Area-Debugging Issue-Enhancement A feature request (enhancement).

Comments

@rkeithhill
Copy link
Contributor

If the user modifies, add or removes a variable in the debug console during a debug stop, that should be reflected after execution of their command.

We will probably need to re-fetch the variables as we can't rely on examining the executed expression for simple variable assignment. The user could be using Add/Clear/Remove/Set-Variable or they may be manipulating the variable drive.

@rkeithhill rkeithhill added the Issue-Enhancement A feature request (enhancement). label Dec 3, 2015
@daviwil
Copy link
Contributor

daviwil commented Dec 3, 2015

One problem we'll have here is that VS Code doesn't give us a way to notify the editor that variables have changed need to be refreshed. We may be able to ask for this though!

@daviwil daviwil modified the milestone: Backlog Dec 31, 2015
@rkeithhill
Copy link
Contributor Author

OK that has been addressed by the VSCode team. Yay!
vscodechangedvariable

@daviwil
Copy link
Contributor

daviwil commented Feb 2, 2016

Awesome news.

@rkeithhill rkeithhill reopened this Feb 2, 2016
@rkeithhill
Copy link
Contributor Author

Oops. Re-opening this as it is a separate issue from the variable dirty indicator and it is not fixed. :-)

@daviwil
Copy link
Contributor

daviwil commented Feb 2, 2016

Ahhh I guess it's not being updated when the user types in something that changes a variable value :) Makes sense. We'd need some way to signal variable changes to them. I wonder if this is even something they'd be interested in adding? Will probably require a feature request here:

https://github.com/Microsoft/vscode-debugadapter-node

@rkeithhill
Copy link
Contributor Author

If they want to better support REPL friendly languages I think they would want this. I also think it would be slick if they allowed the user to edit a variable's value directly in the "variables" tree view while the debugger is stopped. Of course, the debug adapter would need to support such an operation.

@daviwil
Copy link
Contributor

daviwil commented Feb 2, 2016

I seem to recall that they have the desire to allow variable editing, but I can't remember if that was a bug on the VS Code repo or from some e-mail thread. Either way, I think you're right, they'll definitely need to have the variable tree up to date for REPL friendly languages.

@TylerLeonhardt
Copy link
Member

Circling back to this. If I modify the value in the debug console and step over in the debugger, the value does change:

image

Is this what this issue was about or was it more about changing the variable and have it immediately updated in the debug pane?

@daviwil
Copy link
Contributor

daviwil commented Dec 7, 2017

Right, they don't give us a way to notify the UI that the variable has changed "out of band" so there's currently not a way to accomplish this (that I'm aware of).

TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this issue Feb 26, 2019
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this issue Feb 26, 2019
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this issue Feb 26, 2019
…th-tweak

Fixed issue PowerShell#58, extension install path needs to specify version in path
@andyleejordan andyleejordan removed this from the Backlog milestone Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Debugging Issue-Enhancement A feature request (enhancement).
Projects
None yet
Development

No branches or pull requests

4 participants