This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-01
Channels
- # announcements (3)
- # babashka (17)
- # beginners (163)
- # bristol-clojurians (1)
- # calva (18)
- # chlorine-clover (17)
- # clj-kondo (13)
- # cljs-dev (50)
- # cljsjs (3)
- # cljsrn (13)
- # clojure (218)
- # clojure-dev (5)
- # clojure-europe (9)
- # clojure-italy (10)
- # clojure-nl (8)
- # clojure-uk (107)
- # clojurescript (25)
- # conjure (163)
- # cursive (63)
- # data-science (9)
- # datomic (38)
- # docker (1)
- # figwheel (34)
- # figwheel-main (3)
- # fulcro (15)
- # graalvm (1)
- # helix (12)
- # jobs (3)
- # juxt (5)
- # kaocha (3)
- # lein-figwheel (2)
- # leiningen (6)
- # luminus (2)
- # malli (1)
- # meander (12)
- # nrepl (4)
- # rdf (2)
- # re-frame (2)
- # reagent (7)
- # reitit (5)
- # remote-jobs (2)
- # rum (1)
- # shadow-cljs (65)
- # spacemacs (27)
- # tools-deps (18)
- # vim (19)
- # xtdb (2)
in the fulcro book, it talks about server with this function
(defn wrap-api
"Fulcro's API handler"
[handler]
(fn [request]
(if (= "/api" (:uri request))
(server/handle-api-request
server-parser
{:config config}
(:transit-params request))
(handler request))))
I think that is working, thanks alot Chris 🙂
@UEC6M0NNB JFYI there’s a template for F3 with all those things pre-configured https://github.com/fulcrologic/fulcro-template
yes I finally checked the template and saw it, which is what Chris showed .. thanks for reminder
but server/handle-api-request now only accepts 2 args not 3 as it used to .. confused as to which params to include
In fulcro 3 we are seeing root refreshes, but these root refreshes are not re-rendering the current route. We are using (route/immediate …)
and a didComponentMount
function to load the entity for the given route.
The root refresh should be re-rendering the route. Did something change in fulcro 3 so that a root re-render does not refresh the router children?
so make sure you’re querying for the change, not manually pulling stuff in render from state or something
and that you targeted the data correctly…perhaps it isn’t hooked up, so props really are not changing
also make sure your tree (in total) is connected…i.e. that things have initial state. That should not be any diff from f2, though