This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Provide context for "unknown provider" errors. #8135
Labels
Milestone
Comments
The issue is that It's definitely doable, but would require a bit of refactoring across the codebase Would you like to tackle it and send a PR? |
I've never worked on the Anuglar.js codebase. I was hoping you guys could take care of it. |
ocombe
added a commit
to ocombe/angular.js
that referenced
this issue
Oct 21, 2014
ocombe
added a commit
to ocombe/angular.js
that referenced
this issue
Oct 21, 2014
ocombe
added a commit
to ocombe/angular.js
that referenced
this issue
Oct 21, 2014
ocombe
added a commit
to ocombe/angular.js
that referenced
this issue
Oct 21, 2014
ocombe
added a commit
to ocombe/angular.js
that referenced
this issue
Oct 21, 2014
ocombe
added a commit
to ocombe/angular.js
that referenced
this issue
Oct 21, 2014
Yay! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When you get an error like this:
The stack trace is exclusively inside of Angular code, and there is nothing in the error that says which controller's instantiation, or any other object's instantiation, the error is coming from.
There should be enough context to detect where the issue is happening. This is currently very hard to debug.
The text was updated successfully, but these errors were encountered: