Fulcro 2.5.8 is up on Clojars. Fixes a bug in server-side rendering reported by @levitanong, and a websocket bug that where early sends to the server could cause errors while the websocket was establishing. Also fixes a bug where :component could be nil within mutation handlers if the component had no query.

hmm, I can't use qualified keywords for my route params because the fulcro syntax for routing tree use prefix: param/...

;; current fulcro syntax
(r/routing-tree
  (r/make-route :my-screen
    [(r/router-instruction :router [:my-screen :param/x])]))

;; my dream syntax so qualified keywords work
(r/routing-tree
  (r/make-route :my-screen
    [(r/router-instruction :router [:my-screen {:param :qualified/x}])]))

yep. The built-in routing is tuned for use with URI-based parameters, which are not qualified. Feel free to write your own. The code for the existing (non-dynamic at least) routing stuff is very little code.

The routing tree is a very simple thing I threw together to set idents on more than one router at once…but it is just that: a mechanism to combine setting multiple idents on routers into a single mutation. There’s nothing magic about it unless you want to integrate with code splitting.

(defcard-fulcro repayment-state-card
                Root
                {}
                {:inspect-data true
                 :fulcro       {:started-callback
                                (fn [app] (df/load app :foo loan-comp/RepaymentItem {:target (df/append-to *[:REPAYMENT-LIST :singleton :repayments]*)}))}

                 })

Either initial-state or started-callback?

@eric.shao initialState will happen first since it goes at app initialization process, right after that your started-callback will be triggered

@wilkerlucio I want to load one {} or a [] to append to the initial-state’s list. There are three situations 1: when I don’t provide fulcro-started-callback, the initial-state’s list [] will show correctly. 2:when i df/load a {} it will fail 3:when i df/load a [{}] it will replace the initial-state’s list (instead of appending to that list) and report

for append must target an app-state vector.
(vector? (get-in state data-path))

If the initialState happen first, there should be a [] , and it should be appended instead of replace, right? where is the problem?

@tony.kay does fulcro support running the app “server-side”? Like, creating a fulcro client, running loads, fulcro networking etc…

@levitanong no, but if you follow the patterns in the book all of your mutations will have helpers that can be used to simulate just about any action on the server

the HTML5 routing sections talk about this

Not sure why you’d want to “run it”…how would you interact with it? Once it’s on the initial screen events are needed to “drive it” to some state

and since those “events” are always mutations, simply having those in functional form on the server gives you exactly what you want without any “machinery” in the way

@tony.kay The use case is when, for example, I need a set of itineraries that tell the user how to get from one latlng to another latlng. If I want to SSR, then the html I serve should already have those itineraries out. I was thinking that if, when the server receives such a request, it instantiates an app (a client running on the server, in other words), to perform requests from another server (the server the client-client would talk to)

if I could do that, it would be easier to reason about

plus, lots of nice code reuse

sounds like a nightmare to me 😜

think of all of that machinery that can break and make it “not work”…debugging, setup, testing, devops

you already have the functions on the server to return the data, right?

the problem is, i don’t.

the server is primarily a webserver. it doesn’t hold the routing, reverse geocoding, etc…

(by routing i mean in the google-maps way)

ok, so, do your users have to be logged in for this?

currently no. that’s something that’s definitely in the roadmap though.

so don’t SSR

not the logged-in pages

you’re creating work that simply isn’t going to do you much good

the login stuff is primarily for preferences, so it’s safe to be rendering the stuff

and is going to cause a lot of pain

the motivation for SSR right now is SEO

right, and SEO someone’s specific iternerary???

that’s silly 🙂

the itinerary thing is a simplification 😛

Your best bet is really to use CLJC for the client mutations, and do the manipulation of data and only data on the server, then render that with SSR

“loads” will have to be implemented to do JVM-based networking if you need to hit other servers to satisfy external data needs

but the merge functions in Fulcro will work on the server against state maps, so you can get very close to complete sharing of code

i see

it is the advantage of pure rendering to begin with

(and the single language on full stack)

you’re already getting a lot 🙂

i do suppose the statefulness of the instantiated app would be overly complex

and maintaining two ways of dealing with networking…along with the alternate paths wthin Fulcro itself…it’d be a constant source of inconsistencies andbugs

the thing that actually pushed me over into asking about instantiating an app though, is in the case of invented-root-level-keyword loads.

and at the end of all of that probably wouldn’t save you hardly any coding, since you could have already used CLJC shared code to “run arbitrary” operations server-side

because client-side, i have something like :placename->location and :location->placename. Both touch “places”, but fill up complementary deficiencies in information

as opposed to using an ident

and i wasn’t sure how to marry those invented keywords with the merge function

or maybe i know how to make it work, but it’s just one kind of mess that I wanted to cover up with a different kind of mess. 😜

you know about merge-component?

all of the auto-normalization is available on the server

and integrate-ident…both in primitives.

oh, those seem new!

work on a normalized state map

nope…been there for a long time 🙂

the ! form of them are mutations, and the non-`!` form can be used on server or inside of mutations

got it! thanks @tony.kay 😄

cool…yeah. Instead of a load, you just merge

http://book.fulcrologic.com/#_normalization_initial_state_server_interations_and_mutations