I am open to these for areas where the data type in the list is represented in the extension API already (eg Breakpoints). For others, like variables, that would involve having to think about how that type should look presented to an extension, which would take more effort.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

I guess we actually have this for variables already

I guess we actually have this for variables already

We do, the ask is to consider this for some of the other views

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

I am open to these for areas where the data type in the list is represented in the extension API already (eg Breakpoints). For others, like variables, that would involve having to think about how that type should look presented to an extension, which would take more effort.

I definitely understand the difficulty or that this isn't a trivial feature. But at the same time, when it comes to the debug adapter interface, we have a clear spec to adhere to. That's the API - and in a sense, no more, no less (though I'm sure there's always a bunch of new cool magical stuff one can add).

I think it would be neat if VSCode therefore exposed this functionality in a "bi-directional" fashion (sort of) as it's already well defined in the DAP spec. The debug adapter knows what data it gives VSCode, the DAP spec is clear on life times and object references and therefore it should not be that troublesome to pass that data back and forth - even outside of a normal "debug adapter request chain"; since the spec is clear that, for instance, variablesReference: 1 is only valid until the next resume request.

I don't know if this rant made any sense, but it's an attempt to spark a discussion in hopes of possibly moving something forward.

Proposed contribution points covering this request can now be found in these PRs:

• Add viewContainer contribution point #212499
• Add debug window context menu contribution points #212501

cc @roblourens @isidorn