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
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Hello.
There's one more priority-related bug in 1.2.
1.2.2 is now ok when using controller on ng-include but there's one more related bug:
ng-init doesn't affect ng-include.
It can be fixed with setting it's priority higher than in include directive, like:
The priority of ngInit is adjusted to occur before ngInclude, and after
ngController. This enables ngInit to initiallize values in a controller's
scope, and also to initiallize values before ngInclude executes.
Closesangular#5167Closesangular#5208
jamesdaily
pushed a commit
to jamesdaily/angular.js
that referenced
this issue
Jan 27, 2014
The priority of ngInit is adjusted to occur before ngInclude, and after
ngController. This enables ngInit to initiallize values in a controller's
scope, and also to initiallize values before ngInclude executes.
Closesangular#5167Closesangular#5208
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello.
There's one more priority-related bug in 1.2.
1.2.2 is now ok when using controller on ng-include but there's one more related bug:
ng-init doesn't affect ng-include.
It can be fixed with setting it's priority higher than in include directive, like:
Jsbins:
with 1.2.2 - http://jsbin.com/oliGUvud/1/edit?html,output (digit 1 is not there)
with 1.0.8 - http://jsbin.com/EfudOZAF/1/edit?html,output (digit 1 is there)
The text was updated successfully, but these errors were encountered: