warn when default provider overrides custom provider.
- Dominant language
- TypeScript
- Stars
- 101k
- Forks
- 27.5k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 288
Description
### Which @angular/* package(s) are relevant/related to the feature request?
_No response_
### Description
I spent some time debugging why my custom ErrorHandler wasn't being provided, it turns out it was being overridden by a default provider further down in the provider list. It would be nice to have a warning in this situation.
### Proposed solution
n/a
### Alternatives considered
n/a
Contributor guide
Research direction
The issue does not name a package, file, test, or entry point. Start by tracing Angular's provider-resolution path for a custom ErrorHandler and the default provider, then review the comment thread for the intended warning behavior. Done means an agreed warning is implemented and covered for the reported override scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100