title: Angular 2 best practice: binding an object vs binding its properties
body: <p>Is it best for a child component to have inputs of an object's properties and change emitters, or to two-way bind to the object like so:</p>
  
  <p>Example 1</p>
  
  <pre><code>&lt;parent-component&gt;
    &lt;child-component [exampleInput]="object.val" 
                     (valueChanged)="updateObjectValue($event)"&gt;
    &lt;/child-component&gt;
  &lt;/parent-component&gt;
  </code></pre>
  
  <p>vs Example 2</p>
  
  <pre><code>&lt;parent-component&gt;
    &lt;child-component [(obj)]="object"&gt;&lt;/child-component&gt;
  &lt;/parent-component&gt;
  </code></pre>
  
  <p>where example 2's child component would handle the updateObjectValue logic.</p>
  
  <p>In our code right now, a component like this currently has 4 inputs and 2 outputs, and if reducing to 1 property by binding it directly to the object is fine that'd be awesome</p>