You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 9.1, the aspire dashboard by default collapses child resources. This is fine when everything works fine, but hides errors if they occurs
What you see when initially opening the dashboard - everything looks fine.
What you see after expanding the sql server resource - the database is unhealthy.
Expected Behavior
If a resource is in an abnormal state, I'd expect to see this somehow. Either by having resources expanded by default, or having some kind of aggregation / icon indicating something is abnormal about the sql resource, encouraging me to expand it
The simplest fix would be to expand child resources by default.
Also, we should have some persistence of expanded/collapsed resources so that if you collapse a resource, then navigate to another page and back again, the resource is still collapsed.
Also, we should have some persistence of expanded/collapsed resources so that if you collapse a resource, then navigate to another page and back again, the resource is still collapsed.
An "expand all" / "collapse all" option would be a nice companion to that.
Is there an existing issue for this?
Describe the bug
In 9.1, the aspire dashboard by default collapses child resources. This is fine when everything works fine, but hides errors if they occurs
What you see when initially opening the dashboard - everything looks fine.
What you see after expanding the sql server resource - the database is unhealthy.
Expected Behavior
If a resource is in an abnormal state, I'd expect to see this somehow. Either by having resources expanded by default, or having some kind of aggregation / icon indicating something is abnormal about the sql resource, encouraging me to expand it
Steps To Reproduce
Exceptions (if any)
No response
.NET Version info
Anything else?
The text was updated successfully, but these errors were encountered: