Can I wrap my whole React app in

<ThirdPartyEmailPasswordAuth> ... </ThirdPartyEmailPasswordAuth>

while still requiring auth in some place and not others?

Hey @Artyom

My usecase is that I want to access session info in a bunch of places, but when I wrap a component in

<ThirdPartyEmailPasswordAuth> ... </ThirdPartyEmailPasswordAuth>

, it almost always means I have to create a sub-component and it adds boilerplate

We plan on making this possible. But for now, it’s not advisable cause if you use wrap even our pre built UI around this, it will cause an infinite loop when visiting the email verification screen.

Ok noted

But if you do not wrap our pre built around this, you can wrap all the other routes with it and provide the requireAuth=false prop to it.

Aha, okay, good to know

Finally, the other limitation this has now is that it won’t work with server side rendering. Again, we are working on solving that too.

Is there a GH issue I can subscribe to re/ wrapping the whole app?

Thanks, subscribed!