[Enhancement, Epic] Improve debug experience #27016
Labels
area-architecture
Issues with code structure, SDK structure, implementation details
proposal/open
t/enhancement ☀️
New feature or request
Milestone
Description
Today when working on a maui App the debugger experience isn't great, when we inspect a member, it doesn't show useful information at first glance, and some important values are at the bottom of a long list, so would be great if we can improve that with the usage of
DebuggerDisplay
.Example of not useful information:
When debugging the popup will show the
ToString
value of that type which isn't very usefulExample of the need to find a useful information:
In order to find the
ItemsSource
orSelectedItem
on picker, I need to expand that popup and scroll over all properties before it.And some values are recursive:
Here I'm inspecting a
layout
variable, which is aVerticalStackLayout
, and I would like to see its Children, but when I inspect it says that Children is a Window, and it ends in an infinite loop inside the Window. The expected result is thisPublic API Changes
We should use the
DebuggerDisplay
attribute to improve the debugger experience, showing useful information at first glance.Here's the expected result:
Useful information right way:
(maybe we should add the type?)
Intended Use-Case
improve debug cycle on devs that create apps and work on .net maui framework.
The text was updated successfully, but these errors were encountered: