@reefersleep Have you considered wrapping the React comp into a higher level one, or only exposing the necessary props? That way you reduce the complexity of the interop as the children returning functions hurst my head sometimes when interop. I am using it from reagent that way with no problems. [code for component in a snippet below...] and the use it from reagent as usual given i have required the react comp as dnd.. here i show just a sketch of the code to use the above react comp... but it is that simple data is a board made of subBoards.. I am using js camel casing as it is fed into the react comp

(def board-data  {
    :name  "a board for thinking nice thoughts", 
    :subBoards: {
        :one  [{:id 1 :content "some content..."}]}})

[:> dnd {:boardData (clj->js board-data)
:getItemStyle (fn [board-name is-dragging-over] ...)
         :getListStyle (fn [draggable-style is-dragging] ... )
         :itemRenderer (fn [content] ...)}] ;;<<<--------------------------- return the react component there

@fj.abanses you’re right that the back-and-forth interopping is pretty horrendous to follow. I plan to wrap it in more accessible functions once I’ve got it working 🙂

I’m at work currently, so I’ll take a closer look at what you’re saying later tonight. Thanks for chiming in!

@reefersleep 👍

hey guys, writing here hoping that one of the maintainers of reagent sees it. Would it be possible to update the docs of the reagent project? The official http://github.io docs still are for 0.8.0-alpha-2 but the latest version on github is 0.8.0-rc1 🙂

@carocad Checking. It should be automatically updated but I guess I broke the script.

@carocad Updated now.

Nice, thanks :)