again fighting with form-3 components, if I have:

(defn graph [clicked hovered attrs graph-data]
  (log/debug "Init: clicked" clicked)
  (log/debug "Init: hovered" hovered)
  (log/debug "Init: attrs" attrs)
  (log/debug "Init: graph-data" graph-data)
  (r/create-class
   {:display-name "graph-container"
    :reagent-render graph-render
    :component-did-update (fn [this] .....how do I get the individual props here? ...)
    :component-did-mount (fn [this] .....or here? ...))

I tried:

(let [state (r/props this)]
                             (log/debug "graph-did-mount" state)
                             (graph! state))

but now I have many (same passed to the rendered btw)

@richiardiandrea one of the ways to do it is the following

(defn component-form-3 [arg1 arg2 arg3]
  (reagent/create-class
    {:component-function
     (fn [arg1 arg2 arg3] [:div])

     :component-did-update
     (fn [this]
       (let [[_ new-arg1 new-arg2 new-arg3] (reagent/argv this)]
         ; do something
         ))}))

uhm interesting

let me try

(reagent/argv this) inside :component-did-update can be destructured into the same args as passed to the component + 1st argument will be something else

I am interesting in did-mount as well, I am trying, a big thanks!

same signature, I believe

@kishanov works in did-mount as well yes!

this definitely needs a blog post 😉

@richiardiandrea I started recalcictrant with this kind of difficulty in mind

https://github.com/pesterhazy/recalcitrant

oh cool interesting

if you use the "new-props" mixin, the function will simply get the (new) props as arguments, just like the render fn

reagent's handling of lifecycle methods is opaque, the goal is to make it a bit more transparent

the pattern you were looking for (do something both on mount and on update) is pretty common in my experience

yeah, I see that now with d3

re-com components are smooth to use, this stuff is hard-core and not as simple as it should be

yeah you need form-3 components in a couple of scenarios

- XHR requests or other network activity like websockets (if you choose to tie them to the component) - timers - direct dom manipulation - resource cleanup - multimedia (canvas, webgl) - imperative web APIs (video)

luckily you can often stash away the side-effecting complexity in a wrapper Higher Order Component

yes the thing is that I need to re-render my d3 graph (direct DOM) on every mouse event