hi everyone. what’s a good way to restrict users from accessing a private route? basically if they’re not logged in, they should be redirected to login page..

at the moment, my routes are dispatching set-active-page action, that determines which page component to load. should I be doing this logged-in? check at events level?

IMO I would prefer to do this at the HTTP level, not in the app

ex have one "public" app that might have a login form and other things unauthorized users can access, once they've logged in they are redirected to the private route that has the "private" app

these can all be built in the same project, using module splitting

so do you mean 2 different re-frame apps?

essentially yes. same code base, two different apps

this might depend on how you're authenticating

at the moment it’s all SPA. So initially I land on Login page and I’m using JWT authentication and then I’m setting an access token in my local storage + re-frame db. so let’s say I have two routes - /about-us and /dashboard. If I type in http://mysite.com/dashboard and visit the page as a guest, at the moment I’m getting a partially rendered page, as there is no user info set and dashboard needs the user ID to query some stuff via graphql. so that’s what I’m trying to solve basically