@jarvinenemil SSR does work, but the old template branch probably isn’t up-to-date. I think the basics are covered in the book…really isn’t much more to it than the dom-server macros can be used in CLJ-land to generate strings…you just need to pass the correct props tree to the root. Generating the props isn’t so hard, since you can write all logic in CLJC, and use the same code you used on the client to generate props on the server…there are a few helper functions that can build a db for you on the server based on component initial state, which is the most common case for an initial render; however, if you’re trying to implement SSR that shows some HTML5 routed link, then you might find that you’ve got a bit more work to do. The good news is that Fulcro will run headless in the JVM, so you can create a client with a loopback remote and essentially move it through states until you have what you want.

I do not consider headless Fulcro to be battle-hardened. I do not personally use it that way, and don’t know if anyone else in the community does. I have seen no bug reports, but that means very little, really.

The DOM stuff outputting strings does have tests around it, and should be pretty good…but it is also an aspect of the library that I do not currently use in any projects, so it has been low priority for me to beef it (or the docs) up any. Contributions welcome.

Is there a way to tell a load to not delete keys when the entity it pulls from the remote has fewer keys than where it’s loading it into? I’m using multiple comps with the same ident and different numbers of keys (summary and detail), but the one with fewer keys is causing the extra keys to get deleted when it loads. hmm I guess it’s complicated because it’s difficult to differentiate between a query using fewer keys vs the keys having been deleted on the server. Cache invalidation is one of the hard things of CS

Thanks for the excellent answer @tony.kay

Hi, I've been watching the excellent videos by @tony.kay. I am able to use href for dynamic routing, but when I type the URL in, it returns 404. How can I intercept the URL before it gets to the server?

@hadilsabbagh18 you don’t, you have to make the server respond with the index page for all valid routes, and then once your app is loaded look at the URL and fix your application state

I’m having a strange problem with a couple of non-fulcro UI components not rendering until the next render cycle (using the keyframe2 renderer):

(do
  (debug "RENDER DataEntryDate" DataEntryDate)
  (ui-datepicker {:selected DataEntryDate
                  :onChange #(when (inst? %)
                               (log/debug "date change" %)
                               (set-value! this :sitevisit/DataEntryDate %))}))

remember that rendering is predicated on shouldComponentUpdate, which looks for prop changes…if props don’t change: no render….otherwise kr2 renders everything

so it’s behaving as if the datepicker’s :shouldComponentUpdate is false, but then it’s true on the next round

oh interesting, I just switched it from using interop/react-input-factory back to interop/react-factory and now it’s working fine which makes sense because the component isn’t what react-input-factory is made for. not sure why I was using that in the first place

ah, yes…the input factory expects there to be a controlled value that is a string, and it caches it in component-local state…should only really be used for inputs that you type into