-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Full path in debug callstack #30686
Comments
You can hover over the name to see the full path of the name. |
@weinand thank you. |
Could we render the full path and simple use right-aligned text ellipsis to mask the overflow? |
Thanks for the suggestions however rendering the full path would give more details to an already clutterd UI imho. |
To avoid the clutter when always showing the full path we could only show those segments from the end of the path that allow to distinguish files with the same name, e.g. something like this:
With this approach most callstacks will continue to look compact and only those with duplicate file names will need more space. |
I like this idea, it goes well with some other places in the workbench where in tabs we show path of a file only if the file name is duplicated. |
Oh, I didn't know that. So even better! |
From @ubershmekel on June 5, 2017 21:18
I have an app with
index.js
that's calling my library that has an entry point ofindex.js
which relies onnode_modules/express/lib/router/index.js
so my stack trace is entirelyindex.js
with no way of telling which part of it is actually in my code.Is there a way to give a user-configurable option or perhaps expand the path when there's room for it?
Related to:
Copied from original issue: microsoft/vscode-node-debug#146
The text was updated successfully, but these errors were encountered: