-
Notifications
You must be signed in to change notification settings - Fork 234
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
Comments
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! |
Awesome news. |
Oops. Re-opening this as it is a separate issue from the variable dirty indicator and it is not fixed. :-) |
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 |
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. |
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. |
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). |
…th-tweak Fixed issue PowerShell#58, extension install path needs to specify version in path
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.
The text was updated successfully, but these errors were encountered: