Throw a more useful error when unable to resolve an nonexistent class. #16

johnyanarella opened this Issue May 17, 2012 · 1 comment


None yet
1 participant

johnyanarella commented May 17, 2012

When the Injector is asked to resolve an identifier that references nonexistent (or non-required) class, the changes in Issue #11 cause it fail with an error related to availability of classReference.singleton rather than letting the developer know that the class was not found.

Current error message:

TypeError: 'null' is not an object (evaluating 'classDefinition.singleton')

It should instead tell the developer the class definition wasn't found.

Add better error handling and reporting for this situation.

@ghost ghost assigned johnyanarella May 17, 2012


This comment has been minimized.

Show comment
Hide comment

johnyanarella May 18, 2012


Scheduled for inclusion in v0.6.6.


johnyanarella commented May 18, 2012

Scheduled for inclusion in v0.6.6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment