Expose NGxxxx errors through the global ErrorHandler
#42957
Comments
|
This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list. You can find more details about the feature request process in our documentation. |
|
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends. Find more details about Angular's feature request process in our documentation. |
|
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage. We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package. You can find more details about the feature request process in our documentation. |
Which @angular/* package(s) are relevant/releated to the feature request?
No response
Description
The framework includes an error reporting mechanism that reports errors through the console window of the browser or the debug window of the IDE. The list of possible errors can be found at https://angular.io/errors/.
It would be great if we could have the option of reporting those errors directly inside an Angular application.
Proposed solution
Optionally, expose NGxxxx errors through the global error handler of the framework that is available at https://angular.io/api/core/ErrorHandler so that:
Alternatives considered
N/A
The text was updated successfully, but these errors were encountered: