-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
Stop supporting debug.logToDebugConsole command #34700
Comments
Removing this only makes sense in november. First in october we have to create a solution for this using the debug api. |
I will do this on October 23 ;-) |
I can also look into this, just wrote down a note for myself :) |
I've created an API request for this. |
Since the API will be proposed in November, we cannot delete this in November. |
@weinand should I create and assign this to the December milestone? |
Let's wait until we know more about Xmas... |
It seems to only support |
@Alphapage That is only possible from a debug adapter. As an example, you can checkout node debug 2 and find when he sends the |
@Alphapage expandable objects need an active debug session behind them (so that the UI can request more data on expand). When outputting an object from an extension, then there is not necessarily a debug session active. |
As you told, I think I was going to the wrong direction: I just need to add an UI panel to the extension to be able to navigate the object. |
This was done in January / February it seems |
Currently we support a 'debug.logToDebugConsole' command.
https://github.com/Microsoft/vscode/blob/a38db8e0a5ca9b651fd0484faefb17d706400cac/src/vs/workbench/parts/debug/electron-browser/debugCommands.ts#L25
Instead we should introduce API and deprecate this command.
The text was updated successfully, but these errors were encountered: