You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use without ng-include, well done.
I have checked the user is same scope wheather using ng-include or not.
I can't understand what is defferent. How to can I fix it?
The ng-include update value parent scope through user prototype. But validator event binded in ng-include's scope and triggered by container's scope.
So @kelp404 and @genuinefafa solution is should working. But I don't want making meaningless controller.
If I make some form with modal(http://angular-ui.github.io/bootstrap/), controller scope different with scope. Modal controller have only form logic. But I just add a controller for validator. This is bad for my project.
I want to find better solution.(Because I love this project and I want keep this lib in my project.)
Activity
kelp404 commentedon Jul 22, 2014
Hello @victorkim
I think the $scope in ng-include and the $scope at container are different.
You should replace $scope as one in
ng-include.genuinefafa commentedon Jul 22, 2014
Another solution is to use a controller in the form. Controllers are better suited for this casses, than $scope itself.
rubydoc commentedon Jul 23, 2014
Thanks for answer.
I checked angular-validator code.
The ng-include update value parent scope through user prototype. But validator event binded in ng-include's scope and triggered by container's scope.
So @kelp404 and @genuinefafa solution is should working. But I don't want making meaningless controller.
If I make some form with modal(http://angular-ui.github.io/bootstrap/), controller scope different with scope. Modal controller have only form logic. But I just add a controller for validator. This is bad for my project.
I want to find better solution.(Because I love this project and I want keep this lib in my project.)
genuinefafa commentedon Jul 23, 2014
@victorkim I understand where you are going, and I agree with you.
Maybe it's time to improve the validator if no other solution is found. ;)