This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-05
Channels
- # adventofcode (41)
- # bangalore-clj (4)
- # beginners (283)
- # boot (62)
- # clara (9)
- # cljsrn (3)
- # clojure (112)
- # clojure-brasil (1)
- # clojure-greece (1)
- # clojure-korea (6)
- # clojure-russia (99)
- # clojure-spec (29)
- # clojure-uk (12)
- # clojurescript (34)
- # clojurex (5)
- # core-logic (1)
- # cursive (31)
- # datomic (30)
- # devcards (5)
- # editors (19)
- # emacs (31)
- # events (5)
- # garden (4)
- # hoplon (137)
- # lein-figwheel (3)
- # luminus (4)
- # mount (7)
- # off-topic (7)
- # om (18)
- # om-next (3)
- # onyx (88)
- # proton (1)
- # protorepl (6)
- # re-frame (48)
- # reagent (15)
- # spacemacs (41)
- # testing (1)
- # untangled (2)
- # yada (18)
@pesterhazy @martinklepsch I guess that bit bit me. I didn’t use a map as props data, so I got nil. :-S
yeah it's far from obvious
So are you supposed to use only the first argument for props data in Reagent — and the rest of the arguments won’t trigger a re-render when they change?
I don't think that's correct
personally I usually use the first argument (always a map) as it makes things easier
but more arguments to trigger rerenders
@borkdude reagent props =! react props
any changing argument will trigger a re-render
@martinklepsch That’s what I’ve always assumed. This is why the behavior of r/props
is a bit weird, right?
absolutely 🙂
reagent just sticks all the reagent props in a single react prop
hello folks - has anyone ever tried css variables inline yet?
section "Nested calc() with CSS Variables” of https://developer.mozilla.org/en/docs/Web/CSS/calc
tried here but no luck with i.E.
[:section
{:style {:--heightSection height}}