This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-03
Channels
- # adventofcode (6)
- # bangalore-clj (1)
- # beginners (15)
- # boot (4)
- # cider (14)
- # clara (1)
- # cljs-dev (1)
- # clojure (115)
- # clojure-art (1)
- # clojure-france (1)
- # clojure-greece (1)
- # clojure-korea (9)
- # clojure-russia (1)
- # clojure-spec (62)
- # clojure-taiwan (1)
- # clojure-uk (18)
- # clojurescript (5)
- # component (1)
- # cursive (3)
- # datascript (2)
- # datomic (17)
- # devcards (2)
- # editors (4)
- # emacs (65)
- # events (2)
- # funcool (4)
- # hoplon (92)
- # jobs (6)
- # london-clojurians (1)
- # luminus (1)
- # midje (2)
- # mount (1)
- # off-topic (1)
- # onyx (51)
- # protorepl (6)
- # re-frame (116)
- # reagent (7)
- # ring (2)
- # spacemacs (2)
- # specter (4)
- # untangled (1)
- # yada (1)
Is it possible in reagent-forms to bind to dynamic bits of a document? something like:
(row … [:input {:field :text :id :person1.person.full-name}])
(row … [:input {:field :text :id :person2.person.full-name}])
where :person1
and :person2
are added to the document atom?it seems like in theory it should work a la {:field :text :id (sub-item row-entry :person.full-name)}
, but what gets computed when might get tricky. . .
@borkdude https://www.martinklepsch.org/posts/props-children-and-component-lifecycle-in-reagent.html
@pesterhazy Thanks. Looks like this doesn’t tell me more than I already knew though. In did-component-update it’s not possible to get the newest props, only the previous ones?
@borkdude Use r/props
for current props, and function arguments for previous ones
@juhoteperi I think I tried it, but don’t know why I didn’t use it eventually. I’ll try this monday again, thanks
It's explained in Martin's blog post