legacy maintenance release

(2016-05-14) diff

This is a release of the legacy branch, primarily to fix the $scope destroy ordering issues introduced in 0.2.16, as well as adding $scope.$resolve to enable "route-to-component-template".

We recommend all users to try the 1.0.0 alpha and report any issues it causes with your application. Read the known breaking changes between the legacy and 1.0 branches.

BC-BREAK

In 0.2.16 we delayed the ui-view $scope destroy() until after all animations were completed. This was a mistake, and we're reverting it in 0.3.0.

The original issue that we tried to address: #1643

We are switching back to 0.2.15 behavior. The scope is now destroyed as soon as the view is swapped out. This allows cleanup to happen in response
to the $destroy event. If you need to do things after the animation, we've put the promise on the element.data('$uiView') in #2562

Bug Fixes

• state: Inject $state at runtime to force initialization (de3a04a7, closes #2574)
• ui-sref: update ui-sref-active/eq info when params change When ui-state dynamicly changes (9698ec4d, closes #2554)
• ui-state: update ui-sref-active/eq info when ui-state dynamicly changes watchers, make sur (abb3deba, closes #2488)

Features

• resolve: Put resolve values on the scope as $scope.$resolve

  This enables easier "routing-to-component-template", i.e.,

  .state({ name: 'foo', 
    resolve: { thing: (MyService) => MyService.getThing() }
    template: '<my-component component-input="$resolve.thing"></my-component>'
  });
  

• uiView:

  • Fire the $onInit hook (b090ca03, closes #2559)
  • Put $animate promises on element.data('$uiView') closes #2562 closes #2579 (fde64e18)