-
Notifications
You must be signed in to change notification settings - Fork 269
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
Hide DevTools Console output when attached to a debug session #403
Comments
Honestly, I don't think it makes much sense for us to include a limited/one-way console when instead we should just direct users to JS debug. I'll update with a Deprecation notice directing users to JS Debug, and we can remove entirely in a future update. |
Hmmm. Actually, I guess the one case it might be useful is attaching to a target we are not using a debug session for. I'll discuss with the team if the best course of action is removing entirely or just disabling when attached to active target |
This is an upcoming scenario now. |
@codepo8 this is already checked in. Re-closing |
My mistake. Not checked in yet, but will be checked in today :) |
Added in the latest version of the extension |
This seems to cause some confusion (microsoft/vscode#125071) and is redundant when launching from a js-debug session which already has output in the Debug Console
The text was updated successfully, but these errors were encountered: