No description provided.

This is a good opportunity for a PR
Code pointer https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/browser/debugActions.ts#L635

"Copy Path" is a bit weird, maybe "Copy Name"?

"Copy Path" is a bit weird, maybe "Copy Name"?

"Copy Name" usually means copying a particular property name, whereаs I need the whole chain from root (global, window, etc) and ending with selected property/variable.

Actually "Copy Name" wouldn't harm to have as well. There is also a scenario when I go into prototype of an object (or even several levels of prototypes deep) and I need the path without __proto__ in between - for this right now I need to do the thing depicted in the gif above and also manually remove any __proto__ in the result (let's call it "Copy Path (inherited)" or something).

But this may wait for another day. Right now it would be nice to have just the own path. Thank you.

@bpasero Copy Name does not work imho. We could go with "Copy Full Name", "Copy Evaluate Name"
@weinand thoughts?

Even though copy path sounds a bit weird I think it makes it clear for the user what to expect.

Yeah, up for ideas, "Copy Name" is not ideal either. I am just correlating "Copy Path" with file paths typically.

Well, people at Lodash call it path sometimes. Mongoose does the same as well

Also copying path means capturing array indexes as well. In case of multidimensional arrays it would mean only indexes - [5][0][1][67][4][0]. "Name" would be highly misleading in this case.

some ideas:
Copy expression
Copy expression path
Copy evaluation
Copy evaluation path
Copy eval expression

"Copy expression path" and "Copy evaluation path" work for me

Variants:
Copy as expression path
Copy as evaluation path

I don't think "evaluation" is a good word for this. You probably use it internally, to get values to dispaly in the inspector. But from the consumption perspective it has nothing to do with eval. Or do I see it wrong?

Maybe "Copy path as/for expression"?

Any user that uses the REPL (aka debug console) knows what evaluation means because she is using it all the time...

"Copy path as expression" sounds strange because a user has selected a variable not a path.

So my variants from above tried to address this by introducing the "as" but they left out the "variable".
The full name would be:
Copy variable as expression
Or
Copy variable as path expression

Any user that uses the REPL (aka debug console) knows what evaluation means because she is using it all the time...

I'm not saying the user doesn't know what eval means - I'm saying the user associates evaluation with either evaling in console or through eval() method (if there is one in the language). I'm not speaking for everyone, but I do not associate eval with context inspection.

Copy variable as expression

If I would see such a menu item - I would think it does value stringification or something like that.

After a discussion with a team we settled on "Copy as Expression"
Thanks for feedback.