Work around a reparenting issue in RadSideDrawer.

hdeshev · hdeshev · commit 0270da0c6e50 · 2016-04-28T16:33:23.000+03:00
Solves the problem of attaching a node and immediately moving it to another
location in the visual tree without Angular noticing. That breaks the next
attach as it will attach nodes to the new location instead of the original
one.

This should not be supported. Revert once we ship a fix for RadSideDrawer.
diff --git a/src/nativescript-angular/renderer.ts b/src/nativescript-angular/renderer.ts
@@ -114,11 +114,17 @@ export class NativeScriptRenderer extends Renderer {
 
     attachViewAfter(anchorNode: NgView, viewRootNodes: NgView[]) {
         traceLog('NativeScriptRenderer.attachViewAfter: ' + anchorNode.nodeName + ' ' + anchorNode);
-        const parent = (<NgView>anchorNode.parent || anchorNode.templateParent);
+        //HACK: The anchor.templateParent precedence and child.templateParent
+        //assignment are a workaround for RadSideDrawer.
+        //Remove it once we ship the fix in the RadSideDrawer directives.
+        const parent = (anchorNode.templateParent || <NgView>anchorNode.parent);
         const insertPosition = this.viewUtil.getChildIndex(parent, anchorNode);
 
         viewRootNodes.forEach((node, index) => {
             const childIndex = insertPosition + index + 1;
+            //Remember the template parent in case someone moves the view element
+            //before Angular attaches the next view.
+            node.templateParent = parent;
             this.viewUtil.insertChild(parent, node, childIndex);
             this.animateNodeEnter(node);
         });
