<p dir="auto">I just came across an error message that, in my opinion didn't really tell me what the problem was.</p>
<p dir="auto">I was setting up a simple *ngFor <code class="notranslate">*ngFor="#mode in modes"</code></p>
<p dir="auto">Yet, obviously I got an error because I put "in" instead of "of", however the error was<br>
<code class="notranslate">Can't bind to 'ngForIn' since it isn't a known native property (template info)</code></p>
<p dir="auto">It's clearly a stupid mistake, and now that I've seen it once, I understand the error. However first looking at it, I was stumped. I don't personally have suggestions as to what It should be, though perhaps the community does. (If it's deemed worthy of a rewrite)</p>
<p dir="auto"><strong>I'm submitting a ...</strong>  (check one with "x")</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[ ] bug report =&gt; search github for a similar issue or PR before submitting
[x ] feature request
[ ] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question"><pre class="notranslate"><code class="notranslate">[ ] bug report =&gt; search github for a similar issue or PR before submitting
[x ] feature request
[ ] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong><br>
ViewChildren and ViewChild are searching for child / children only,</p>
<p dir="auto"><strong>Expected/desired behavior</strong><br>
They should search for descendents also.</p>
<p dir="auto"><strong>Reproduction of the problem</strong><br>
steps for reproduce:<br>
Lets say you have component1 that declare component2 inside of it,<br>
and component2 declare component3 inside of itself.<br>
component1 can't use ViewChildren to get component3.</p>
<p dir="auto"><strong>What is the expected behavior?</strong><br>
I would expect component1 to find component3</p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong><br>
I want to find descendents of specific type and not only children</p>
<p dir="auto"><strong>Please tell us about your environment:</strong></p>
<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.0-rc.4</li>
<li><strong>Browser:</strong> [Chrome 52]</li>
<li><strong>Language:</strong> [ TypeScript 1.8]</li>
</ul>