you mean some kind of middleware?

Hi all, I followed [this](http://blob.tomerweller.com/reagent-import-react-components-from-npm) tutorial but cannot find any info about the 😆 macro. Is this a reagent one?

Sorry, the :> macro.

@profgra It is not a macro, it just a normal keyword and Reagent implementation uses that to adapt React class to Reagent, same as adapt-react-class:

https://reagent-project.github.io/news/news060-alpha.html

@profgra Nothing specific to Reagent or :> here, you just can't use #([]) to build a vector using anon function literal

The problem is that #( ) will call what ever you have inside it, so it will try to call the vector as function

you could use #(vector :> (bs 'MenuItem) ...) instead

@juhoteperi OK I understand. Or I could use #(identity […]). Thank you very much.

or (fn [] […]) which does the same thing but is more concise

Any idea what might be causing that? Or should I look for fault in the other component?

@mrchance when you render you are reset!-ing layout. Which will cause a further render, which will reset! layout, etc. That would be my guess if you are seeing an infinite number of calls.

So I'd look at your compute-layout function ... my guess is that each time it is being called it is calling the #(reset layout %) function given to it as a 2nd argument.

@mikethompson That sounds reasonable, but why doesn't it always happen? It's fine if I mount the component by itself

The looping only starts when I mount the other one

Hm, maybe some interplay with figwheel? You're right though, compute-layout does always call it, so it should be easy to fix

Thanks