title: When using the angularjs "controllerAs" syntax is it still good practice to have a container object?
body: <p>I've recently found the controllerAs syntax and I'm wondering if it precludes the need for wrapping your scope variables in objects in order to get the reference. </p>
  
  <p>Sorry I'm probably not asking clearly but what I mean is are both of the following declarations as safe as each other or should I still use a model object when using controllerAs to avoid issues with nested scopes? </p>
  
  <p>Old method - </p>
  
  <pre><code>$scope.model = {
      myData: "test"
  }
  
  &lt;div ng-controller="myController"&gt;
      &lt;input ng-model="model.test" /&gt;
  &lt;/div&gt;
  </code></pre>
  
  <p>ControllerAs - </p>
  
  <pre><code>$scope.myData = "test"
  
  &lt;div ng-controller="myController as myC"&gt;
      &lt;input ng-model="myC.test" /&gt;
  &lt;/div&gt;
  </code></pre>