Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

fix($controller): throw better error when controller expression is bad #10910

Closed
wants to merge 1 commit into from

Conversation

caitp
Copy link
Contributor

@caitp caitp commented Jan 29, 2015

Previously, the error was a JS runtime error when trying to access a property of null. But, it's
a bit nicer to throw a real error and provide a description of how to fix it. Developer ergonomics
and all that.

Closes #10875

Previously, the error was a JS runtime error when trying to access a property of `null`. But, it's
a bit nicer to throw a real error and provide a description of how to fix it. Developer ergonomics
and all that.

Closes angular#10875
caitp added a commit that referenced this pull request Jan 29, 2015
Previously, the error was a JS runtime error when trying to access a property of `null`. But, it's
a bit nicer to throw a real error and provide a description of how to fix it. Developer ergonomics
and all that.

Closes #10875
Closes #10910
@caitp caitp closed this in dda65e9 Jan 29, 2015
@steowens
Copy link

This is first rate code. Impressive.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

angular cannot read property '1' of null is not a useful error message.
3 participants