These are some notes we made while working through how to bolt react navigation together. https://confluence.condense.com.au/display/IZ/Navigating+between+screens - the relevant bit is the RootStack :ref but perhaps the context is interesting.

I do see value in https://github.com/seantempesta/cljs-react-navigation having tried without a wrapper.

Or did I read that right. The screen containers get the navigator as a prop. That might be what you are asking.

I actually figured that out in a different (and more re-frame-ish) way just now

(defn app-root []
  [:> appnav/central-app-switch {:ref (fn [this] (dispatch [:set-root-navigator this]))}])

this basically does it - root navigator becomes a part of app-db and then you can reference it in effectful handlers

(reg-fx
  :navigate
  (fn [[root-navigator route params]]
    (.dispatch root-navigator (navactions/navigate-to route params))))

(reg-event-fx
  :handle-login-success
  validate-spec
  (fn [{:keys [db]} [_ session-info]]
    (println db)
    {:db (-> db
         (assoc-in [:dcn-session] (-> session-info
                                      (update-in [:userInfo :gender] keyword)
                                      (update-in [:userInfo :siteRoles] (fn [v] (map #(keyword %) v))))))
     :navigate [(:root-navigator db) :Main]}
    ))

it is embarrassingly simple

thanks for the link though, it’s very helpful, too!