Interface TreeChanges

A UI-Router Transition is from one Path in a State Tree to another Path. For a given Transition,
this object stores the "to" and "from" paths, as well as subsets of those: the "retained",
"exiting" and "entering" paths.

Each path in TreeChanges is an array of PathNode objects. Each PathNode in the array corresponds to a portion
of a nested state.

For example, if you had a nested state named foo.bar.baz, it would have three
portions, foo, bar, baz. If you transitioned tofoo.bar.baz and inspected the TreeChanges.to
Path, you would find a node in the array for each portion: foo, bar, and baz.

todo

show visual state tree

Hierarchy

TreeChanges

Indexable

A UI-Router Transition is from one Path in a State Tree to another Path. For a given Transition,
this object stores the "to" and "from" paths, as well as subsets of those: the "retained",
"exiting" and "entering" paths.

Each path in TreeChanges is an array of PathNode objects. Each PathNode in the array corresponds to a portion
of a nested state.

For example, if you had a nested state named foo.bar.baz, it would have three
portions, foo, bar, baz. If you transitioned tofoo.bar.baz and inspected the TreeChanges.to
Path, you would find a node in the array for each portion: foo, bar, and baz.

nodoc

Index

Properties

Properties

After the Transition is successful, these nodes will be active.
Because they are entering, they have their resolves fetched, onEnter hooks run, and their views
(component(s) or controller(s)+template(s)) refreshed.

Note that a state that is reloaded (due to parameter values changing, or reload: true) may be in both the
exiting and entering paths.