Skip to content

Remove all custom Error classes #4317

Closed
@jelbourn

Description

@jelbourn

As of TypeScript 2.1, extending Error has issues: it generates a non-trivial amount of code and it doesn't property pass messages through. We also don't really get any benefit from them, since Angular clobbers them anyway.

We can replace each custom error with a function like throwInputContainerUnsupportedType()

Metadata

Metadata

Assignees

Labels

P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgenthelp wantedThe team would appreciate a PR from the community to address this issuerefactoringThis issue is related to a refactoring

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions