I'm using re-frame with secretary and running into a small issue.

When I refresh the page at say "#/widgets/1/whatsits/42"

At app start I'm manually invoking secretary/dispatch! on the current token in history

That triggers a re-frame handler that updates the name of the current page to render

but it seems that it misses a few cycles, because it always starts rendering the default page for a few ms then jumps to the correct page

Is there a canonical way to make sure that all of the routing logic is setup and triggered correctly before starting rendering that I'm missing?

@aboekhoff: out of curiosity are you using the luminus template?

@nfisher: I started with the re-frame frontend only template. I think that might be my problem. I probably need to init the db, init the routes, and only then hook the navigation. I'll give that a try tonight. Thanks!

@aboekhoff: Do you use accountant.core/dispatch-current! somewhere? In my understanding that's what triggers route on startup.

@nidu Just using plain secretary. Definitely targeting users with older browsers so HTML5 history is off limits for now. I think my problem is incorrect ordering of side-effects during init.