Too Many Resources
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
We're starting to get larger and larger app hosts . Whislt these are really powerful, the dashboard is starting to become more and more complex
For many people, this extra detail causes more confusion than it solves, revelaing revealing a bit too much of how the sausage is being made, and serving to cause more confusion than
In this example from https://youtu.be/u0iK6Bv5BZ0?si=8FroyPDWNtfExa0h, of ~20 resources, 8 are what I'd consider noise, and don't really add a lot.
### Describe the solution you'd like
I'd like to see more ways in which we can control and reduce resources displayed on the dashboard to allow us to focus on what really matters for that App Host. There are a few separate things that would help here, but I also wanted to raise this as a wider issue for some more holistic thinking.
- #13427 (Fixed in 13.1)
- #11603
- #13634
### Additional context
_No response_
Contributor guide
Research direction
Start by reviewing the dashboard example and the related issues #13427, #11603, and #13634 to understand which resource displays are considered noise and what has already been addressed. Done should be an agreed, concrete way to control or reduce dashboard resources without losing important App Host information.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100