hz-field breaks with late binding 'item'

[Tyr Johanson]

Normal usage of hz-resource-property-list will break hz-field because the "item" is loaded asynchronously. Notice the use of a link function which inspects the "item" attribute, but doesn't watch it.

NOTE: A simple work around until this can be made more dynamic is to use "ng-if='ctrl.item'" on the hz-resource-property-list.

Details:
Using hz-resource-property-list on a details view within a routed-details-view. The specific item is provided by the routed-details-view ctrl.context.loadPromise. The natural usage in my template is

<hz-resource-property-list
    resource-type-name="OS::Designate::FloatingIp"
    item="ctrl.item"
    property-groups="[
      ['address', 'ptrdname', 'description', 'id', 'ttl', 'status', 'action']
    ]">
</hz-resource-property-list>

where ctrl.item is set by the result of the context load promise.

$scope.context.loadPromise.then(onGetResponse);
function onGetResponse(response) {
  ctrl.item = response.data;
}