Components.AI: Unify safe status and error presentation
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 281
Description
### Is your feature request related to a problem? Please describe the problem.
Four components duplicate status/footer rendering, and several shells expose raw exception messages while another shows a generic error.
### Describe the solution you'd like
Introduce one shared status/error presentation path with non-leaking default text, localized accessible status, and an opt-in detail template for applications that intentionally expose diagnostics.
### Additional context
Leaf task for #68227 requirements A6 and G5.
Contributor guide
Research direction
Start with requirements A6 and G5 in #68227, then locate the four components and shells that currently render status or errors. Trace their existing presentation paths and compare the generic and raw-exception behavior. Done means one shared path with non-leaking default text, localized accessible status, and an opt-in diagnostic detail template.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- accessibility, frontend, internationalization, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100