You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add CopyVariable PAth to clip option in debugger pane #1328
A clear and concise description of what the problem is that the new feature would solve.
Try formulating it in user story style (if applicable):
As a user, I would like to be able to have access to the path of variable when I am exploring it in the debugging pane of VSCode.
Story:
I often use the debugger to help me find out where I can find the information I need to then add it into my code. For that, I like to add a breakpoint, and go look into the object directly, and then I memorize the name, and simply use intelisense to get to the right spot and add the access to that property / method into my script.
A clear and concise description of what you want to happen:
What would be great thought, is that if it was possible to have access to the path of the dot notation path directly via a right click menu in the debugger pane, something like this:
In red you have the path + the option, and the green text would more or less be what would be copied into the clip board.
Proposed technical implementation details (optional)
I am not sure how this could be done, but if I have some guidance, I would be glad to give it a try ;)
I think this is something that VSCode itself could add since we just hook in to their debugging interface.
We'll follow up with whether this is part of VSCode's debugging API... I will say that it is low priority so if anyone would like to do this investigation, I'm marking it as "Up-for-Grabs".
I've just opened an issue with VSCode asking for an API for this functionality: microsoft/vscode#50598.
This feature would probably depend on changes in VSCode itself though and there are a few other things we're currently working on, which is why it's marked as Up-for-Grabs.
Activity
TylerLeonhardt commentedon May 22, 2018
Hi Stéphane (@Stephanevg), thanks for this! This looks like a cool feature!
I think this is something that VSCode itself could add since we just hook in to their debugging interface.
We'll follow up with whether this is part of VSCode's debugging API... I will say that it is low priority so if anyone would like to do this investigation, I'm marking it as "Up-for-Grabs".
eric-smithson commentedon May 28, 2018
@tylerl0706 Any updates? Definitely a useful feature!
rjmholt commentedon May 29, 2018
I've just opened an issue with VSCode asking for an API for this functionality: microsoft/vscode#50598.
This feature would probably depend on changes in VSCode itself though and there are a few other things we're currently working on, which is why it's marked as Up-for-Grabs.
Stephanevg commentedon Mar 17, 2019
Hi Rob Holt (@rjmholt) Any updates on this one?