Not sure if everyone already knew about this but I am finding https://github.com/rauhs/klang an excellent adjunct to re-frisk and replacement for high-level println/console debugging (I still dump detail to the console)

@andre something i would find really useful is being able to "prime" re-frisk with important keypaths for my app and have them turned into bookmarks into the app-db.

Do you always have to have an event handler registered for every event in re-frame? With the async-flow-fx, I've found myself wanting to listen to events that particpiate in the flow, but are no-op in terms of db and effects. I've put in dummy no-op event handlers but wondering if this is necessary or there is another way.

@danieleneal no other way, currently. Events need a handler

cool thanks! Good to know for sure 🙂

Hey #re-frame'rs, is there a way to schedule a piece of code to be run after the rendering?

I want to scroll to the bottom of a div after I updated it

you might be able to use a form-3 component with component-did-update

but that's not reframe specific, just react

Ho yea, thanks for the quick reply @danieleneal!

(defn scrollBottom! [this]
  (let [o (reagent/dom-node this) #_(.getElementById js/document id)]
    (set! (.-scrollTop o) (.-scrollHeight o))))

(defn my-component [...]
  (let [... subscribscriptions]
    (reagent/create-class
      {:component-did-update
       (fn [this old-argv]
         (scrollBottom! this))
       :reagent-render
       (fn [...] old-render)})))

IIRC, the dom-node method was going to be deprecated by the react team, is it safe to use now?

ah I don't know I'm afraid @lsenta - but you might be right

It doesn't mention anything in the code https://github.com/reagent-project/reagent/blob/78ae18dce28585fc2ba99ccb2bbb975d85386bb0/src/reagent/dom.cljs#L59-L62

ah yeah

https://github.com/reagent-project/reagent/issues/251

Ho yea, that's it

Thanks for finding the link Daniel, I'll keep an eye on it 🙂