Fork me on GitHub
#fulcro
<
2019-11-20
>
defun10:11:38

Hi All, I'm getting the warning when using dynamic-routing in fulcro3.0.10,WARN [com.fulcrologic.fulcro.ui-state-machines:?] - UNEXPECTED EVENT: Did not find a way to handle event :waiting! in the current active state: :routed I don't know what wrong with me

henrik10:11:33

I’m getting that as well, I’ve basically been ignoring it. It seems to be some interplay between the route-handler and the states, but I’m not experienced enough with Fulcro yet to decipher what causes it. https://github.com/fulcrologic/fulcro/blob/673fddbb017c293885aab3f97d99f7e11b20be80/src/main/com/fulcrologic/fulcro/routing/dynamic_routing.cljc#L251

defun11:11:31

oh, I may see what cause it. in the dynamic_routting.cljc file, initialize! call ::uism/beign with event-data, but there is not :target key in the event-data. so finally in the route-handler func, there is not target. As a result the var immediate?'s value is nil, it should be a bug. (defn route-handler [{::uism/keys [app event-data] :as env}] ... immediate? (immediate? target)] (-> (if immediate? ... (-> env ... (uism/set-timeout :delay-timer :waiting! {} deferred-timeout #{:ready! :route!}) ) ... ) .. )

defun11:11:31

oh, I may see what cause it. in the dynamic_routting.cljc file, initialize! call ::uism/beign with event-data, but there is not :target key in the event-data. so finally in the route-handler func, there is not target. As a result the var immediate?'s value is nil, it should be a bug. (defn route-handler [{::uism/keys [app event-data] :as env}] ... immediate? (immediate? target)] (-> (if immediate? ... (-> env ... (uism/set-timeout :delay-timer :waiting! {} deferred-timeout #{:ready! :route!}) ) ... ) .. )

jorda0mega19:11:41

what's the preferred/simplest way of deploying a fulcro app to a server? aws? heroku?

souenzzo20:11:26

Once you build the js, you can serve as static files. I use s3

pithyless20:11:42

Is there a way in Fulcro Inspect chrome-extension to enable Pathom request tracing?(similar to how you can enable request trace in a pathom-viz workspace card)?