Data Inspection: Variable - Object inspection is empty or has random fields
See original GitHub issueSteps to reproduce:
-
Add
Object o = new Object()
variable and Debug application -
Open Debug -> Variables and expand the variable
-
It has random field inside (every time new): Expected: Variable has no fields.
-
Move cursor over Object variable in Editor
-
Data Inspection Popup is empty Expected: Title is Instance of Object or something like that
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Inspecting storage and databases for sensitive data
Instructions for setting up an inspection scan using Cloud DLP in the Google Cloud console, and (optionally) for scheduling periodic repeating inspection scans....
Read more >Inspecting and Changing the Value of Data Elements
The Debug Inspector is especially useful for examining compound data objects, such as arrays and linked lists. Because you can inspect individual items ......
Read more >Cannot call member property on object of this type
Hello, I am trying to reference data stored in another feature layer ... My Hydrant Inspections table does not contain an Object ID...
Read more >All About Missing Data Handling - Towards Data Science
When we say data are missing at random , we mean that missing data on a partly missing variable (Y) is related to...
Read more >FindBugs Bug Descriptions - SourceForge
NP: equals() method does not check for null argument, Bad practice ... MF: Method defines a variable that obscures a field, Correctness.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I believe this may be a VS Code issue - I’ve opened an issue at https://github.com/Microsoft/vscode/issues/56996. I’ll keep this one open for now in case it turns out we’re doing something wrong.
Great! Looks like I was supposed to do some digging, but it slipped through the net. I think they moved over to a new tree implementation since we opened that, so maybe that resolved these quirks. If you do see it again, please let me know and I can do some more digging. Thanks!