Clojurians Log v2

@tkjone thanks! your example works great.

On the frontend side however, how do you initialize when landing on a nested (non-root /) route? I'm using re-frame. The backend is serving the SPA properly now on any path, but on the frontend itself reitit isn't matching the path when I enter the page at a non root path (that is, / works client side but /something/deeper doesn't)

Do you have a simple example of your routing setup + entry point to your app?

Example: this is another simple example of handling front end routing: https://gist.github.com/athomasoriginal/eadc022482c3432943c400cc8eeb1788

importantly i'm also using :use-fragment false

Yeah, the above example should also work with HistoryAPI

(def router
  (reitit/router
    [""
     ["/" {:name :home :view #'home-ui}]
     ["/something-else" {:name :home :view #'another-ui}]]
    {:compile coercion/compile-request-coercers}))

(defn navigate! [match _]
  (rf/dispatch [:common/navigate match]))


(defn start-router! []
  (rfe/start!
   router
   navigate!
   {:use-fragment false}))

(start-router!)

What’s navigate! doing?

(this is from the luminus project generation with +re-frame)

(added the navigate! function)

Yeah, so I just want to see what navigate! is doing. For example, in the gist I provided, mine just updates the match atom. The general idea is i’m trying to isolate where something is going wrong. A quick way to do that is to see if the problem is in your routing logic (reitit) (in my example, routes) or is the problem in the app entry point (in my example current-page)

so browsing to / loads the :home route, but navigating to /something-else loads a blank page as the match is nil.

but that only happens on a fresh page load.

if i load / and then click a button to something-else it works

Should I be seeding it with the initial window location or does reitit frontend pick that up?

navigate! is called with a nil value for match when browsing to /something-else

It should pickup on it. The idea is: • page loads • the url is read + passed to reitit • reitit matches • the match is passed to Reagent I’m not an expert with reitit yet, but can you try updating your routing structure to

[["/" {:name :home :view #'home-ui}]
 ["/something-else" {:name :home :view #'another-ui}]]