title: Placing directive logic inside controller rather than link
body: <p>I have a general question. I've recently seen plenty of examples of people putting all their directive logic in a directive controller (and using it with controllerAs) instead of using link. I do see certain benefits in that: </p>
  
  <ol>
  <li>The directive logic can be easily unit-tested. </li>
  <li>You are seamlessly obligated to use the "dot notation" in your view model, thus prevent unexpected behavior.</li>
  </ol>
  
  <p>As for the disadvantages - once the logic is inside the controller, it is exposed to other directives, as if encouraging developers of other directives to access those variables/methods, even if they are not meant to be accessed from outside.
  I am interested in getting your take on this? How do you organize your code inside the directive.</p>
  
  <p>Thanks</p>