With the release of AngularJS V1.7, the option to pre-assign bindings to has deprecated and removed:
Due to 38f8c9, directive bindings are no longer available in the constructor.
To migrate your code:
- If you specified
$compileProvider.preAssignBindingsEnabled(true)
you need to first migrate your code so that the flag can be flipped tofalse
. The instructions on how to do that are available in the "Migrating from 1.5 to 1.6" guide. Afterwards, remove the$compileProvider.preAssignBindingsEnabled(true)
statement.
Due to bcd0d4, pre-assigning bindings on controller instances is disabled by default. We strongly recommend migrating your applications to not rely on it as soon as possible.
Initialization logic that relies on bindings being present should be put in the controller's
$onInit()
method, which is guaranteed to always be called after the bindings have been assigned.-- AngularJS Developer Guide - Migrating from v1.5 to v1.6 - $compile
What are the use cases when code has to be moved to the $onInit
Life-Cycle Hook? When can we just leave the code in the controller construction function?
Code has to be moved in the
$onInit
function, when it depends on bindings, because these bindings are not available withinthis
in the constructor. They get assigned AFTER instantiation of the component class.Example: You have a state definition like this:
You can bind the result of
myResolve
to your component like this:If you now log out
this.myResolve
in theconstructor
and in$onInit
you will see something like this:So, your constructor should only contain constructing code like:
Every angular specific initialisation and binding or dependency usage should be in
$onInit