@deadghost I'm surprised you'd ever have to use lifecycle functions

If I'm reading you correctly, on bootup, you need to wait for two HTTP calls to suceed, right?

And, until the 2nd one succeeds, you don't want to render the UI (or some part of it)

(defn  main-panel 
   []
   (if-not @(subscribe [:booted?])
      [:div "Loading ..."]
      [full-ui]))

0.8.0-alpha1 is out now https://github.com/reagent-project/reagent/blob/master/CHANGELOG.md#080-alpha1-2017-07-31

I quickly wrote down some upgrade tips also: https://github.com/reagent-project/reagent/blob/master/docs/0.8-upgrade.md

Excited to try it out

I updated a work project to this and used :global-exports with local foreign-lib defs like in the upgrade guide

React-leaflet npm package doesn't seem to yet work directly

Hey, I asked this yesterday, but I've been messing around and still haven't been able to find an answer. How can I call a member function of a component? I tried reacitfy-component but I still wasn't able to call (.memberFunction component arg) because cljs still said that the member function didn't exist

@juhoteperi what error did you see?

WARNING: JSC_JS_MODULE_LOAD_WARNING. Failed to load module "warning" at /home/juho/Source/x/y/node_modules/react-leaflet/lib/Pane.js line 47 : 4

Just found the reason, Closure doesn't support package.json browser field: https://dev.clojure.org/jira/browse/CLJS-2289

didn't know about that field either

I suppose it's a webpack thing?

Browserify also

do you have a pointer to the docs by any chance?

these react event bindings work except for :on-drop. any ideas? 🙂

{:on-drag-start (fn [] (println "drag start"))
 :on-drag-over (fn [] (println "drag over"))
 :on-drop (fn [] (println "drop"))
 :draggable true}

@mikethompson nope not on bootup, my app makes http requests and load resources whenever the url is changed, the nav has to survive this process without re-rendering unless the end data state really has changed.

oops, i needed to prevent default on drag over. user error.