dotnet
[wasm][debugger] Removed internalProperties group.
Fixes https://github.com/dotnet/runtime/issues/75778.
Motivation: https://github.com/dotnet/runtime/issues/75778#issuecomment-1252541452.
It fixes a bug from net 7, so will need backporting.
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
Issue Details
Fixes https://github.com/dotnet/runtime/issues/75778.
Motivation: https://github.com/dotnet/runtime/issues/75778#issuecomment-1252541452.
It fixes a bug from net 7, so will need backporting.
| Author: | ilonatommy |
|---|---|
| Assignees: | ilonatommy |
| Labels: |
|
| Milestone: | 7.0.0 |
Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3091753776
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Started backporting to release/7.0-rc2: https://github.com/dotnet/runtime/actions/runs/3091794256
Also, it would be a good idea to remove all the __* fields that we add to the json for our consumption, before sending them out from the proxy. The tests shouldn't depend on any of those.
@ilonatommy just curious, is VS using the
privatePropertiespart?
It is using it in the meaning: they are displayed. However, the difference between them and result is not stressed in VS - in Browser it is. To visualise, here are two screenshots from the same class in VS and Browser:
Also, it would be a good idea to remove all the
__*fields that we add to the json for our consumption, before sending them out from the proxy. The tests shouldn't depend on any of those.
I agree and Thays already mentioned this idea as well. The PR with it will be out soon.