Question

Normally in all examples/source code of AngularJS modifications of scope is done in controllers. In my directive I need to get some information from another directive (or it’s scope) and put it into scope (so visible in template of directive). As this information is common for all instances of this directive, using scope binding does not sound good for me.

So the only solution I found is to modify instance scope in linking function:

link: function(scope, element, attr, parentCtrl) {      
  scope.data = parentCtrl.someData;      
}

This solution works. Plnkr example

The question: Is it ok according to AngularJS philosophy/style to modify scope in linking function or there is another solution?

Answer 1

Since you are creating isolate scopes in your directives (in your example plnkr), and you want to allow for parents to be ‘somewhere’ in the scope hierarchy (according to your comment to @MathewBerg), I believe your only option is to use the linking function to modify the scope.

(I suppose you could define methods on your MainCtrl that only the child directives should call, but enforcing that would be messy and break encapsulation).

So, to echo what @MathewBerg already said, yes, modify the scope in the directive/linking function.