This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-16
Channels
- # announcements (1)
- # aws (6)
- # babashka (17)
- # beginners (30)
- # calva (12)
- # cider (25)
- # circleci (2)
- # clojure (42)
- # clojure-australia (8)
- # clojure-czech (1)
- # clojure-europe (30)
- # clojure-france (52)
- # clojure-italy (2)
- # clojure-nl (16)
- # clojure-serbia (3)
- # clojure-uk (10)
- # clojurescript (40)
- # core-async (5)
- # cursive (24)
- # datalog (7)
- # datomic (8)
- # emacs (4)
- # events (1)
- # figwheel-main (3)
- # fulcro (2)
- # helix (5)
- # heroku (1)
- # kaocha (6)
- # leiningen (3)
- # malli (11)
- # music (5)
- # off-topic (20)
- # practicalli (1)
- # re-frame (4)
- # react (8)
- # reitit (14)
- # rewrite-clj (5)
- # rum (2)
- # schema (2)
- # shadow-cljs (23)
- # vrac (28)
- # wasm (4)
- # xtdb (12)
- # yada (5)
I've found some problems with the hooks/use-component
function in the fulcro-3.5 branch.
Firstly, the initialize?
option is given the default binding of true
with associative destructuring, but this binding is never used. Instead, the original options
map is passed directly to rapp/add-component!
, so initialisation of state does not happen by default. I assume it is actually meant to be true
by default either in use-component
or add-component!
.
Secondly, the initial-params
option is completely ignored for the first comp/get-initial-state
call because (or {} initial-params)
always evaluates to {}
. I believe the or
should be omitted, since a default binding has already been specified.