Skip to content
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

Cannot Expand Thrown Errors in Node Debug Console #19333

Closed
mjbvz opened this issue Jan 25, 2017 · 3 comments
Closed

Cannot Expand Thrown Errors in Node Debug Console #19333

mjbvz opened this issue Jan 25, 2017 · 3 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@mjbvz
Copy link
Collaborator

mjbvz commented Jan 25, 2017

Testing #15796

  1. Start debugging a node2 program
  2. Run throw {x: 2} in the debug console

Expected
When running console.error({x: 2}), an expandable object is printed

Actual
Only prints the error text in this case

screen shot 2017-01-24 at 7 13 04 pm

@mjbvz mjbvz added debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality labels Jan 25, 2017
@mjbvz mjbvz changed the title Cannot Expand Thrown Errors in Node Debugger Cannot Expand Thrown Errors in Node Debug Console Jan 25, 2017
@roblourens
Copy link
Member

The reason it's a string is that an Error object doesn't look very good when you try to read the multiline stack as an object property. Definitely something to improve in the future though, especially for throwing other objects like this.

@weinand weinand added this to the Backlog milestone Nov 16, 2017
@roblourens
Copy link
Member

This would be a feature request on vscode + debug protocol to give a better way to visualize a multiline string (error + stack) plus an object with expandable props. Feel free to close it though.

Chrome devtools lets me expand the object inline with the error message:

image

image

@roblourens roblourens assigned weinand and isidorn and unassigned roblourens Nov 20, 2017
@weinand weinand modified the milestones: Backlog, On Deck Nov 20, 2017
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Sep 20, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 20, 2018

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Sep 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

4 participants