From 909cabd36d779598763cc358979ecd85bb40d4d7 Mon Sep 17 00:00:00 2001
From: Vojta Jina
Date: Tue, 5 Nov 2013 12:31:20 -0800
Subject: fix($compile): make isolate scope truly isolate

Fixes issue with isolate scope leaking all over the place into other directives on the same element.

Isolate scope is now available only to the isolate directive that requested it and its template.

A non-isolate directive should not get the isolate scope of an isolate directive on the same element,
instead they will receive the original scope (which is the parent scope of the newly created isolate scope).

Paired with Tobias.

BREAKING CHANGE: Directives without isolate scope do not get the isolate scope from an isolate directive on the same element. If your code depends on this behavior (non-isolate directive needs to access state from within the isolate scope), change the isolate directive to use scope locals to pass these explicitly.

// before
<input ng-model="$parent.value" ng-isolate>

.directive('ngIsolate', function() {
  return {
    scope: {},
    template: '{{value}}'
  };
});

// after
<input ng-model="value" ng-isolate>

.directive('ngIsolate', function() {
  return {
    scope: {value: '=ngModel'},
    template: '{{value}}
  };
});

Closes #1924
Closes #2500
---
 xx | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 xx

(limited to 'xx')

diff --git a/xx b/xx
new file mode 100644
index 00000000..e69de29b
-- 
cgit v1.2.3