-
Notifications
You must be signed in to change notification settings - Fork 95
Error: undefined is not an object (evaluating 'directive.messages') #62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello, I've edit it using my settings from the code pen examples. It seems that there is a bug (or not dont know yet) that you should use the growls as an action or result of something. http://plnkr.co/edit/SLWeLg8gOzXWodatWng3?p=preview I've added a button that can be clicked and this toggles a growl notification. I dont know in what usecase you should instantly show a growl when the controller is initialized (something odd happens then). I can look into it |
Yeah, my example is contrived (a reduced test case to demonstrate the bug), though I'll frequently trigger a growl from a service (i.e. not from a user-facing interaction) e.g. when an XHR call has failed. |
+1, I am seeing this too. |
same error
|
I think this is a loading issue or async issue, it works with a button or a server response, I'll look into it this week |
I've run in to this issue when unit testing my code that calls the growlMessages service without the directive. Essentially initDirective is never called so this.directives[referenceId] is undefined. In my unit tests I had to do something like:
|
+1, running into this as well. |
+1 I'm getting this error too. |
+1 ran into this while unit testing too |
+1 |
Any idea what's going on here? plunkr.
The text was updated successfully, but these errors were encountered: