This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-01
Channels
- # adventofcode (66)
- # announcements (12)
- # aws (8)
- # babashka (28)
- # beginners (160)
- # cider (28)
- # clara (22)
- # clj-kondo (5)
- # cljdoc (40)
- # clojure (129)
- # clojure-australia (2)
- # clojure-europe (24)
- # clojure-gamedev (19)
- # clojure-nl (5)
- # clojure-norway (15)
- # clojure-sanfrancisco (25)
- # clojure-seattle (2)
- # clojure-spec (13)
- # clojure-uk (29)
- # clojurescript (14)
- # cryogen (5)
- # cursive (7)
- # data-science (1)
- # datascript (5)
- # datomic (8)
- # deps-new (5)
- # emacs (19)
- # events (8)
- # fulcro (32)
- # graalvm (7)
- # helix (9)
- # kaocha (3)
- # lambdaisland (1)
- # london-clojurians (4)
- # malli (5)
- # meander (32)
- # off-topic (143)
- # pathom (4)
- # portal (32)
- # re-frame (7)
- # reagent (33)
- # reitit (2)
- # shadow-cljs (5)
- # spacemacs (4)
- # tools-deps (30)
- # vim (1)
I have a subform that is setup via comp/get-query
but it seems that the props
of the parent aren’t reflecting the updated values of the subform, while the app state for that subform’s ident does.
@njj but when you print the props of the parent they print on each change but have the old values?
(dom/input
:.form-control
{:type "text"
:value value
:id value
:onChange #(m/set-string! this :value :event %)
:onBlur #(prim/transact! this `[(fs/mark-complete! ~{:entity-ident [:price/by-id _id]
:field :value})
:price/by-id])})
@U0CKQ19AQ Do you think it has to do with the onBlur?
Although, I have seen callback methods passed via the computed props before for updating form values - but I didn’t that that would be necessary in this case.. Since each has its own set of values for the subform
#(m/set-string! this :value :event %)
The name of your field is an unqualified :value
????unless you’re using f2, in which case you’re using ident-optimized render and what you’re seeing is expected behavior
@U010LFZGFEG does that mean that was your problem?
I’m on Fulcro 2, I ended up just flattening the data a bit and making the field value part of the parent form - removing the subform all together
so, all you needed to do was add a refresh to the transaction (a keyword in the parent’s query)
it’s a data-driven refresh model. F3 switched to not needing that as much, but you just tell it a keyword in the parent query to get the parent to refresh
The Fulcro developer's guide recommends java 1.8.x, but I'm running a java 11 openjdk build. What problems should I expect to see if I use java 11?
@ben.grabow AFIK there is no "direct problem", but some other common libraries of fulcro ecosystem, like #datomic, still recommends java8 Also, #shadow-cljs had some problems with newer JVM (I had a issue with the deprecation of nashorn for example). But shadow usually fix this kind of issue very fast (docs/templates/examples can't flow)
what. I never knew.. I guess the book is misleading here? https://book.fulcrologic.com/#Transactions ctrl+f `[( has 73 matches
Like Tony said in Fulcro 3 you don’t have to quote, but you still can. (Calling Mutations just returns a quoted version of them) Many examples in the book are from Fulcro 2 where you had to quote.