You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
As for now session profiles have a :go-to event handler and :go-to* event handler.
The former is responsible for making sure that the application has enough data to perform an authentication check if needed. As soon as that's true, a :go-to* is dispatch.
That one was, up until now, responsible for doing authorization checks (e.g. landing only for non-authenticated users) and, if authorization checks has passed, letting through the actual navigation event.
So that alone would already cry for further division into two handlers - one for authorization and one for navigation. But naming event registrations were blockers here. I really wanted to outermost one to be called :go-to as that's the intention to do.
Recently I realized that it's very much doable nicely with help of re-frame async flow. That :go-to event could look somewhat like this (untested!):
As for now session profiles have a
:go-to
event handler and:go-to*
event handler.The former is responsible for making sure that the application has enough data to perform an authentication check if needed. As soon as that's true, a
:go-to*
is dispatch.That one was, up until now, responsible for doing authorization checks (e.g. landing only for non-authenticated users) and, if authorization checks has passed, letting through the actual navigation event.
So that alone would already cry for further division into two handlers - one for authorization and one for navigation. But naming event registrations were blockers here. I really wanted to outermost one to be called
:go-to
as that's the intention to do.Recently I realized that it's very much doable nicely with help of re-frame async flow. That
:go-to
event could look somewhat like this (untested!):The text was updated successfully, but these errors were encountered: