@pesterhazy Nope, just unsure how it all works. Usually with traditional following construction i initialized all data/events in first let and then in second let - everything that uses changing component props. Can/should i make such split using with-let?

(defn component [...]
  (let [...]
    (fn [...]
      (let [...]))))

anyone notice reagent with the new cljs version “1.9.660” has a warning WARNING: Protocol IFn implements method -invoke with variadic signature (&) at line 61 resources/public/js/compiled/dev/reagent/impl/util.cljs

oh, hah

newer version of reagent is out and I somehow missed it

@mikerod fortunately the warning is harmless, it should work despite the warning

still a good idea to update reagent, but not a necessity

Yeah, I figured

FYI I had a longer question related to doing the reagent upgrade that came up. So long that I just put it in the mailing list https://groups.google.com/forum/#!topic/reagent-project/Q_HaJwWVFBY

@mikerod I wrote reply there

@juhoteperi Thank you. That is extremely helpful and insightful!

> "closed" dependency = closer dependency, if several versions of same package are required, maven will select the one with shortest path: Dependency meditation: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

Thanks, yeah, I’m used to the Maven dep system

(came from jvm, not js 😛 )

How can I return ReactElement from function?

hah, opened a source and immediately found https://github.com/reagent-project/reagent/blob/master/src/reagent/core.cljs#L20

label here - http://recharts.org/#/en-US/api/Pie code example - http://recharts.org/#/en-US/examples/PieChartWithCustomizedLabel

Thanks everyone in the slack!

@edbond often r/as-element is more convenient

What is the correct combination of deps for project.clj for the latest Reagent and React? I've tried bumping them to:

[reagent "0.7.0" :exclusions [cljsjs/react]]
[cljsjs/react "15.6.1-0"]

Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in  React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see 
Warning: Accessing createClass via the main React package is deprecated, and will be removed in React v16.0. Use a plain JavaScript class instead. If you're not yet ready to migrate, create-react-class v15.* is available on npm as a temporary, drop-in replacement. For more info see