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
I have setup a fork that demonstrates the odd behavior in the demo directory. Essentially fields that are generated from within a ng-repeat loop appear to cause cross field validation, apparently confusing which elements to validate and ignoring the validate-on condition. For example you'll be on field A or B which have 'dirty' validate-on conditions and they will not validate until the last field C which has a 'blur' condition is validated
I can see one of the issue from my demo is that I was using the same literal string for the name attribute for each element in the loop. What I've now attempted to do is pass a template expression i.e. {{field.id}} for this value but its breaking at line 178 when attempting to set the validity on the element due to the expression not being evaluated; Its literally seeing name as {{field.id}}
I have setup a fork that demonstrates the odd behavior in the demo directory. Essentially fields that are generated from within a ng-repeat loop appear to cause cross field validation, apparently confusing which elements to validate and ignoring the validate-on condition. For example you'll be on field A or B which have 'dirty' validate-on conditions and they will not validate until the last field C which has a 'blur' condition is validated
[email protected]:micahblu/angular-validator.git
Any help would be appreciated, even if just to point me in the right direction to debug it.
The text was updated successfully, but these errors were encountered: