So just to clarify (hopefully I am accomplishing that), why, when creating
an isolate scope (scope: {} or scope: true) does the scope get the parent
scope's $id although from what I can see the connection (inheritance) is
severed (as the docs say)?
On Wednesday, February 5, 2014 11:55:09 AM UTC-5, Mike Cheel wrote:
>
> Thanks for your reply Sander. The $rootScope (002) never has a parent
> (undefined) yet when set scope to any value (true, false, or {}) the
> $parent.$id is set either to '002' ($rootScope) or the containing scope. I
> guess this confuses me because I expected an isolate scope to not have a
> parent id. What am I missing?
>
> On Wednesday, February 5, 2014 11:30:18 AM UTC-5, Sander Elias wrote:
>>
>> Hi Mike,
>>
>> Can you put up a plunk/fiddle to illustrate what you exactly mean?
>> Apart from that, the scope.$parent will always give a parent, even in an
>> isolate scope.
>> In AngularJS an $ marks an internal property, those are different from
>> whatever you put on there yourself. Don't expect those to behave an normal
>> scope properties!
>> My guess is that you still want to be able to use scope.$apply and
>> scope.$watch, even on an isolate scope don't you?
>>
>> Regards
>> Sander
>>
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/groups/opt_out.
