Fork me on GitHub
#reagent
<
2016-12-05
>
Jacobin03:12:06

thanks guys

borkdude10:12:26

@pesterhazy @martinklepsch I guess that bit bit me. I didn’t use a map as props data, so I got nil. :-S

pesterhazy10:12:13

yeah it's far from obvious

borkdude10:12:02

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?

pesterhazy10:12:08

I don't think that's correct

pesterhazy10:12:27

personally I usually use the first argument (always a map) as it makes things easier

pesterhazy10:12:38

but more arguments to trigger rerenders

martinklepsch11:12:36

@borkdude reagent props =! react props

martinklepsch11:12:52

any changing argument will trigger a re-render

borkdude11:12:18

@martinklepsch That’s what I’ve always assumed. This is why the behavior of r/props is a bit weird, right?

martinklepsch11:12:34

absolutely 🙂

pesterhazy11:12:40

reagent just sticks all the reagent props in a single react prop

michael.heuberger22:12:51

hello folks - has anyone ever tried css variables inline yet?

michael.heuberger22:12:32

tried here but no luck with i.E.

[:section
       {:style {:--heightSection height}}