Is this an anti-pattern in Reagent, or just fine?

(defn foo [arg1] [:div (str arg1)])
(defn bar [arg1 arg2] [:div (str arg1 arg2)])
(defn parent [child]
  [:div
   child])

[:div
   [parent [foo "foo"]]
   [parent [bar "1" "2"]]]

Or this:

(defn precalculated []
  (let [state (r/atom 10)]
    (fn []
      [:div
       (into [:div] (range @state))
       [:button {:on-click #(swap! state inc)}
        "Click me button”]])))

why an anti-pattern? can you explain?

No, I just don’t know

afaik that's exactly how reagent is intended to be used 🙂

ok 🙂

I saw some strange things with re-rendering in the past. Maybe it was due to the use of (foo …) vs [foo …]

What if you use [(decide-which-component-to-use …) “foo”]?

still works fine

there are a couple of things to look out for when it comes to re-rendering

the most important being lazy sequences (avoid them! 👍 for your into above)

another is multimethods (avoid)

I've blogged about this: https://presumably.de/reagent-mysteries-part-2-reloading.html

@pesterhazy can you elaborate a bit more / have any resources on the multimethod code smell? Didn't see it on the blog... 🙂

multimethods are aweseome generally

there's a known issue with reagent however where if you use a multimethod as a component, the component doesn't rerender properly

don't have a pointer to a github issue unfortunately

honestly at this point it's more hearsay, but @pupeno ran into it recently as well I believe

it's a shame because multimethods would make for great (polymorphic) components

Thanks for the heads up. It's directly related to some work that I am doing, so I will keep an eye out. Appreciate it...

if you can identify the issue and create a github issue, that'd be great

@pesterhazy I’ve got my React Virtualized Infinite Loader working now btw. Hooked it up with Re-frame. Thanks for the help.

Np

I remember it working fine about six months ago. I picked up the same projects and now it's not working. Really puzzling and annoying.