when using secretary with reframe is it a common pattern to dispatch multiple events? such as

(defroute "/:id-token" [id-token]
  (re-frame/dispatch [::events/set-id-token id-token])
  (re-frame/dispatch [::events/set-active-panel :home-panel))

In my opinion it’s better to dispatch just one event. That event can have other events as side-effects (for instance :dispatch [::events/set-active-panel]).

I think it’s more or less the same thing - depends on the level where you want to control it

My understanding is that you're supposed to dispatch based on the user's intent, rather than the internal meaning (e.g. of panels). So you should dispatch a "page-navigate-event", and the dispatch handler for that will have conditional behavior for setting the id token.

👆

so that single event handler could in theory update multiple db fields?

if that id-token field is nil im making a call, but i only want to make that call if it’s nil

What is the user doing at that point?

Why is she navigating to that route

the user is going to the home page, if the id-token is not present in the db the page redirects to an sso auth page and redirects back to the home-page with an #id-token1234 appended to it

so it’s on initial load really

so when visiting / the first time, you’ll end up returning to /#token-id and i want that to load the same content as visiting / but with that token-id stored in the app state db

In that case I’d probably have single event called ::show-home-page and it can take id-token as a param. Event handler can then set active panel to the db and trigger other side-effects via effects-map.

In the event handler you can do something like (when id-token [… do something conditional ])

I hope this makes sense to you!

thanks @valtteri i think that helps; will be working on this throughout the week and will definitely post an update. 🙂