-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Test: debug console objects from output #15901
Labels
Milestone
Comments
isidorn
added
debug
Debug viewlet, configurations, breakpoints, adapter issues
testplan-item
labels
Nov 22, 2016
This did not work for me as advertised -- see #16641 |
Oh this is not actually implemented yet @isidorn |
Oh sorry for the misunderstaing, that's why I pinged you on the original issue -> lets move this to january then and unassign people |
FYI: I just tested this with (an unreleased version of) my debug adapter in an insider build of VS Code (Date 2017-01-13T07:03:18.620Z) and it works fine for me. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Complexity: 2
As per #15796 we are now supporting expanding complex objects in repl which are coming from output channels. Have a node program, choose
node2
astype
in 'launch.json', launch your program, open repl and verify:console.log
to print complex objects, these objects can be expanded in replconsole.log
with multiple arguments, likeconsole.log('abc', { d: 123 })
, and they are all visible.The text was updated successfully, but these errors were encountered: