docs/vendor.js
function getParentState(state, rootView) {
    var node;
    if ((node = state[HOST_NODE]) && node.tNode.type === 2 /* View */) {
        // if it's an embedded view, the state needs to go up to the container, in case the
        // container has a next
        return getParentLNode(node).data;
    }
    else {
        // otherwise, use parent view for containers or component views
        return state[PARENT] === rootView ? null : state[PARENT];
    }
}
function getParentState(state, rootView) {
    var node;
    if ((node = state[HOST_NODE]) && node.tNode.type === 2 /* View */) {
        // if it's an embedded view, the state needs to go up to the container, in case the
        // container has a next
        return getParentLNode(node).data;
    }
    else {
        // otherwise, use parent view for containers or component views
        return state[PARENT] === rootView ? null : state[PARENT];
    }
}
function getParentState ( state , rootView ) { var node ; if ( ( node = state [ HOST_NODE ] ) && node . tNode . type === 2 /* View */ ) { // if it's an embedded view, the state needs to go up to the container, in case the // container has a next return getParentLNode ( node ) . data ; } else { // otherwise, use parent view for containers or component views return state [ PARENT ] === rootView ? null : state [ PARENT ] ; } }
Determines which LViewOrLContainer to jump to when traversing back up the
tree in destroyViewTree.

Normally, the view's parent LView should be checked, but in the case of
embedded views, the container (which is the view node's parent, but not the
LView's parent) needs to be checked for a possible next property.

@param state The LViewOrLContainer for which we need a parent state
@param rootView The rootView, so we don't propagate too far up the view tree
@returns The correct parent LViewOrLContainer
Determines which LViewOrLContainer to jump to when traversing back up the tree in destroyViewTree .