-
Notifications
You must be signed in to change notification settings - Fork 68
Tools tip for dictionary shows object hash #45
Comments
As a note, I've started to take a look at this issue. |
After investigating it, this will actually be a big change in The main issue is that the API to get variables only provides users with a way to get a dictionary of key->value which will already be the final representation of the object (and what's shown to the user is later used to get the variable again). To fix this, both the protocol as well as the internal API will need to be changed to allow for object identifiers to be given to variables so that the what's shown to the user does not need to contain that information (which means that the protocol has to be changed to send and receive such an id to get the variable and that mapping of ids->variables must be kept while the thread is suspended). Given that this will touch a good number of places, my suggestion would be already fixing the other related issue which is being able to have a different formatter per-request and try to use json instead of xml as a payload for the responses which return variables. My estimate is around 12 days to have this complete. I'll already start on it, but as it'll take a while until it's actually integrated let me know if there's something I should take a look first given that this will take longer than I anticipated. On the good side, the solution is closer to what the debug adapter protocol expects, so, the integration in |
I will go over the issues and let you know. |
Though this is a dup of #1114, please note the values are more prominent in VSC, hence the issue is worse in VSC than in VS. |
The thing is this is how |
The text was updated successfully, but these errors were encountered: