title: Angular 2 detectChanges vs setTimeout()
body: <p>I'm facing an issue regarding angular 2 change detection.
  I'm using a component which uses the 'onPush' strategy and I've noticed that it's child component don't update them self on update (They themselves also 'onPush') so I've added changeDetector.detectChanges() to my code and it caused <code>Maximum call stack size exceeded</code>.
  I dag up a little bit and wound up doing </p>
  
  <pre><code>setTimeout(() =&gt; {
    this.changeDetector.markForCheck();
  }, 0);
  </code></pre>
  
  <p>And the code worked just fine.
  My question is why angular.detectChanges() cause this error and using setTimeout don't? If I understood currently the setTimeout should run changeDetection also so it pretty much the same, doesn't it?</p>
  
  <p>Is it good practice to use the setTimout like that? </p>