On 2/9/17, 8:38 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>Hi Alex, > >I think the reason that we haven't had problems with numElements is that >no >one use it before. It's true that compiler should catch it even without >using, but it didn't. > >As for the internalChildren - Sankar in his application did find one >scenario with Tabs component where our element was undefined. Do you have time to figure out why element is undefined? Adding defensive code doesn't scale. Eventually it adds up to something. So if 99% of the time the defensive code doesn't do anything we want to understand what it would take to make it 100% so we can remove that code. Thanks, -Alex
