Clojurians Log v2

@thosmos possibly expound version???

@tony.kay Hi, in a state machine, can you provide handler that is always run when entering particular state? Something like :entry handler

FYI

See book. What’s supported is described there. “entering a state” is activate, and no, there is no automation at that point, but you’re already in a handler and can do whatever you want as a precondition yourself. Having handlers run on state transitions (without an explicit event) leads to bad behaviors like accidental infinite transition loops (handler transitions, runs a handler that transitions back, runs a handler that transitions again, etc.).

Thank you Tony, i’ve saw the book I just didnt saw anything about that, that’s why I asked. But fully noted, no info in book = not implemented

@tony.kay I think that https://book.fulcrologic.com/#_initial_state_3 is incomplete and may lead to incorrect behavior. Correct pre-merge for a dynamically loaded component (with ident such as [:org/id <some id>] and :will-enter with dr/route-deferred a df/load! inside) that includes a router and, possibly, is itself under a router, should be in my experience something like:

:pre-merge     (fn [{:keys [data-tree state-map]}]
                    (assoc data-tree
                      :my/child-router   (merge
                                           (comp/get-initial-state MyChildRouter)
                                           (get-in state-map ; <--- this is crucial!
                                                   (comp/get-ident MyChildRouter {})))))