nested directives doesn't inherit scope from each other?

[fxck]

Consider this code

<div directive-one="['foo', 'bar']">
    <directive-two />
</div>

where directive-one has this setting

scope: {
  arr: '=directiveOne' 
}

and directive-two doesn't have any scope param defined(not that directive-two is not inside directive one's template for a reason, directive two doesn't really have a template and is there just to provide data from it's attribute for child directives). I would have thought that arr would be accessible in directive-two's scope, but it's not scopes looks like this

where 00B is from directive-one and 00A is from directive-two..

plunk's here http://plnkr.co/edit/T1sm9z2EjMFwVoGpdoGk?p=preview

is this behaviour expected?

[caitp]

yes, this is the expected behaviour. You should not use an isolate scope without a template, only the isolate scope directive's template will use the isolate scope. Nothing else will, unless you explicitly use the isolate scope when transcluding.

[fxck]

So the only option I have is to not use isolated scope, which would mean that I'd have to $eval the attribute instead of using scope: '='? Is there any reason why you can't use @, &, = without creating an isolated scope?

[caitp]

Is there any reason why you can't use @, &, = without creating an isolated scope?

Because you just can't, basically. The directive API is kind of crazy, and the problems with it are probably not going to be solved in 1.x :(

You can still do everything that @/&/= do manually, just without those little helpers.

You have the option of not creating a new scope at all (by omitting the scope parameter), and the option of creating a new, not-isolate scope by setting scope: true