Fix issues with context and undefined children

[bkniffler]

No description provided.

[apollo-cla]

@bkniffler: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

[tmeasday]

Would it be possible to add some tests that highlight why the if (child) checks are needed? It would avoid reversions in the future..

[tmeasday]

Why do we need these? I thought new Component did that for us?

[bkniffler]

These three constructors are valid for react:

constructor() {
super();
}

constructor(props) {
super(props);
}

constructor(props, context) {
super(props, context);
}

But only the last one is covered by new Component(props, context). At least thats what I suppose.

[bkniffler]

I can't do it immediately, got some work to catch up. But there is a lot of situations where a child can be null, a stupid example: <MyComponent>{user.isAdmin ? <AdminPanel /> : null}{user.isSuperAdmin ? <SuperAdminPanel /> : null}</MyComponent>.

[tmeasday]

Thanks @bkniffler , see 800ce40