Once I implemented the chapter: Email Verification I get the warning:
Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render. Or maybe you meant to call this function rather than return it.

This warning is generated for the following router components:
|
<Route exact path={ROUTES.HOME} component={HomePage} /> |
|
<Route exact path={ROUTES.ACCOUNT} component={AccountPage} /> |
|
<Route exact path={ROUTES.ADMIN} component={AdminPage} /> |
Their common denominator is that they all compose over the HOC: withEmailVerification. When I comment out:
then the warning disappears.
I tried googling for answers and found this: https://stackoverflow.com/a/48458532/4400976 but I do not see how our HOC is being misused as a regular component as the answer is alluding to. It is the exact same pattern we are using for withAuthorization and withAuthentication; e.g. a declaration of HOC that embeds the argument Component by means of a closure and that we use for our compositions accordingly. But the warning would not come about then.
Once I implemented the chapter:
Email VerificationI get the warning:This warning is generated for the following router components:
react-firebase-authentication/src/components/App/index.js
Lines 31 to 33 in 316a175
Their common denominator is that they all compose over the HOC:
withEmailVerification. When I comment out:react-firebase-authentication/src/components/Home/index.js
Line 16 in 316a175
then the warning disappears.
I tried googling for answers and found this: https://stackoverflow.com/a/48458532/4400976 but I do not see how our HOC is being misused as a regular component as the answer is alluding to. It is the exact same pattern we are using for
withAuthorizationandwithAuthentication; e.g. a declaration of HOC that embeds the argumentComponentby means of a closure and that we use for our compositions accordingly. But the warning would not come about then.