@olegakbarov We occasionally use HoC (Higher Order Components) by just doing this (untested)

(defn greeter
  [name]
  [:div "Hello: " name])

(defn decorate 
  [& HoCs]
  (into [:div] HoCs))   

;; markup: 
[decorate [greeter "Spot"] [greeter "Fiddo"]]

Inspect HoC (you are using clj-devtools I hope)

Got the first version done of my latest Reagent app: http://mtg.arturgajewski.com

@artur nice work. What backend storage to you use?

@gamecubate This is just a front app. The API is mentioned in the About section. This app fetches data from the http://magicthegathering.io API and renders data as needed. Pictures of the Magic cards are loaded from Gatherer.

Working on listing different sets of Magic throughout the years and listing cards belonging to each set.

Upcoming work includes ability to add each card to personal Deck for proxy card printing

Oh I see. Are you using cljs-ajax for the fetches?

When this is done, I will open source code on github

Nice.

I use cljs-http.client to fetch data asynchronously with go function

go is part of core.async IIRC (haven’t used channels yet so not sure)

If so (using async), I am impressed. I’m newish (30 days-) at CLJS so haven’t tackled that beast yet. On the list of TODOs, along with re-frame.

Reagent is great, all things considered.

Yup, you'll see when I put the code on github

Hmmm.... is there a way to dispatch secretary one back step? Trying to make a "Go back" button.

@artur: I think you should be able to do something like this - http://www.w3schools.com/jsref/met_his_back.asp

how would you do it in clojurescript?

I would just use JS interop to call it directly

(history.back js/window)

something like that?

Not sure of the exact syntax, check out http://www.spacjer.com/blog/2014/09/12/clojurescript-javascript-interop/ for better info than I can give you (I refer to it every time I need to do JS interop, thankfully infrequently for me).

@artur shaun has supplied you with a really good resource, but if you want a shortcut use (.. js/window -history back) which results in the js window.history.back()

When you are wrestling this stuff, this can be a useful site: http://app.klipse.tech/ (takes a while to load) Enter your cljs top left, wait for 3 seconds and see the generated js top right

Nice link thanks Shaun. And thanks Mike for the tip, will try it tomorrow. Now off to bed o/

When using :should-component-update with a react component that's being used in a JSX application, the first parameter appears to be the old properties. How do I get the changed/updated ones?

Example {:should-component-update (fn [new-props _] (.log js/console new-props))} shows the new props under the .-props new-props key, but when I access it that I just have the old prop values.

yrgh, I’m updating a year-old project that has dependencies on reagent, reagent-forms, reagent-utils, and react-bootstrap

is there a way anyone has found to not make that a giant ReactJS incompatibility mess

what do you mean by "ReactJS incompatibility mess"?

at least some of those projects have opinions on which react version you get to have

when a particular API disappears, like nameToPath, that causes problems

specifically, I just had to bisect my way to a react-bootstrap that works with reagent 0.5.1

Simple solution is just to use stable React version (15.*)

Also, nameToPath sounds like Closure problem instead of React. Maybe missing dependency.