Clojurians Log v2

I think I ran into this just a few days ago: https://clojurians.slack.com/archives/C68M60S4F/p1726493996708549 try using {:route-params {:video/id "hello"}}.

(defsc VideoPlayerMinimum [this {:video/keys [id] :as props}]
  {:query [:video/id]
   :ident (fn [] [:component/id ::VideoPlayerMinimum])
   :route-segment ["video-player-min"]

   :will-enter (fn [app {:video/keys [id]}]
                 (dr/route-deferred [:component/id ::VideoPlayerMinimum]
                                    (fn []
                                      (merge/merge-component! app VideoPlayerMinimum {:video/id id})
                                      (dr/target-ready! app [:component/id ::VideoPlayerMinimum]))))}
  
  (dom/div
   (dom/p "Props: " (str props))
   (if id
     (dom/p "Video ID: " id)
     (dom/p "No video ID provided"))))/

(comment 
  (rroute/route-to! SPA VideoPlayerMinimum {:video/id "hello"})
  )

Thank you so much! I’ve decided to start to documenting “how I use Fulcro to solve problems, and solve Fulcro problems” here: https://github.com/realgenekim/fulcro-hints/wiki/Home:-Hints-on-Using-Fulcro-and-Fulcro-RAD 🎉

So happy that it’s working!!! And mystery solved! Thank you @alex.sheluchin @jj974!!!

heh I don't think my suggestion was correct, but you're welcome anyhow 😛 I look forward to seeing you build up that resource.

@genekim did you try adding the route param to your route segment?

:route-segment ["video-player-min" :video/id]

@genekim currently it is not possible to ⭐ your repo b/c it is empty, perhaps add a readme to it or something? 🙏

@holyjak you can star it from https://github.com/realgenekim?tab=repositories&type=source

Thank you, @tony.kay. I think I have both of these issues sorted for the most part. As a minor correction for future readers, for route->url, it's just something like {:route ["landing-page"]} (can include :params if needed), rather than a :target key.

(thanks, I’ll fix the typo above)

As a further reference, I want to point out this section of the book: https://book.fulcrologic.com/#_route_segments_and_changing_routes Which talks about the motivations for how it works. Particularly this paragraph:

Notice that since the command to control the route is up to you, so is the path you pass to it. This makes it easy to do things like alias one path found in the URI to a different UI path, which is useful when you restructure the real UI but would like to maintain support for old paths that users may have bookmarked.

URL -> Function you create/control to parse the URL into fragments -> Function you create that can rewrite the fragments to a new path -> Dynamic Routing change-route!

Thanks for the references. I read that section last a long time ago, so it's definitely time for a refresher.

It’s funny. Some sentences I wrote really stick out at me as important, but then it is very difficult in a 300 page book to make the same things happen for the reader. You can only do so many “IMPORTANT” and “NOTE” kinds of things before no one pays any attention to them.

Yeah, I guess when you're using the book as reference the important part is whatever's most relevant to your case. I've always wandered what the numbers would look like if my code comments had a read counter.

You’d have to modify the html5 history and handle this special case to map it internally to something non-empty. Just like you do with a web server / (or in this case nothing) will NEVER return a resource. It is an error. You have to insert code that, when it sees an empty URL, translates that to a path with some content (e.g. on web servers this would be like index.html)

dynamic routing does NOT handle URL mapping. It takes a vector of (non-empty) strings and tries to find components that match that vector. An empty string is considered an error

With the new-html5-history, does it require more than just changes to the two url->route and route->url functions? My thinking is that these should be the only things that need new definitions. I'm working on this now but can't quite seem to get it to behave. I also have a default route flicker when I refresh a view-only form. Not sure if this is related to what I'm trying to modify.

Correct. The url->route needs to take the “empty” url case and turn it into something like {:route ["landing-page"]}

Remember also that Fulcro is a pure View(state). So, flicker will occur when you choose to render a state that isn’t what you want. To avoid this flicker, you’d do something in the wrapper above the routes to prevent rendering the state until it has stabilized. E.g. :ui/ready? flag that when false shows a loading animation or something…then, once you’ve initialized the app completely, change the flag to true.