-
Notifications
You must be signed in to change notification settings - Fork 35
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
Custom Callback not working #14
Comments
+1. Same problem here. |
These lines seem to be the problem. Scope is referencing child scope instead of the parent where the callback would exist. Adding $parent to both scope calls fixes the issue for me. |
+1. Same problem here. |
We need to check scope.$parent for the inputNameSetArgs callback Closes webadvanced#14
Thanks for fixing! :) just my two cents. What if we add ngArgs to isolated scope then we pass it in html? . With this, we don't have to worry about the parent/child scope. FYI. I'm still new in AngularJs. |
Hi,
I tried using your directive, but can't seem to get the Custom call back working:
HTML:
Controller:
It is always sent as
{ value: val }
instead of{ test: val }
. I was thinking of sending the string straightaway without any JSON array.Am I doing anything wrong in my code?
The text was updated successfully, but these errors were encountered: