Hey. So I posted this issue... https://github.com/reagent-project/reagent/issues/333

And messaged yogthos briefly. He suggested I come here to gather thoughts

Looking for any input and specifically if reagent-project/create-reagent-app could be set up and used as the repo for it

TLDR idea is create-react-app just for reagent. Zero config, “sane defaults”, and specifically for JavaScript developers with no Clojurescript experience

The tenzing tool is the closest I’ve found, though of course it requires some choices

I do wish a Dan Abramov like character backed by Facebook cash would descend upon clojurescript to make my life easier 🙂

@lee.justin.m what would make it easier?

No promises but there’s a make things easier movement afoot

@eveko okay, I’m back for more punishment. Picking up where I left off, I’ve come up with the following:

However, when I try to add this to a normal reagent component with [my-component {}], I get nastiness in the browser

Error rendering component (in frontend.core.current_page > > home-page > > > > > > > > frontend.ui.component.main.my_component > reagent221)

and Uncaught Error: Invalid arity: 8

@venantius How about

(def bar-chart (reagent/adapt-react-class js/Recharts.BarChart))
(def x-axis (reagent/adapt-react-class js/Recharts.XAxis))
(def y-axis (reagent/adapt-react-class js/Recharts.YAxis))
(def cartesian-grid (reagent/adapt-react-class js/Recharts.CartesianGrid))
(def tooltip (reagent/adapt-react-class js/Recharts.Tooltip))
(def legend (reagent/adapt-react-class js/Recharts.Legend))
(def bar (reagent/adapt-react-class js/Recharts.Bar))

I don’t think you are using @venantius correctly. You typically use that inline

You ended up making bar-chart just a cljs vector

I’m not sure what else happens beyond that

Using the :> though would look like:

[:> js/Recharts.CartesianGrid {:strokeDasharray "3 3"}]

you didn’t give more of a stacktrace so I don’t know exactly what happened

let me give that a shot

sorry I can paste fuller stacktraces, give me a mo

@mikerod that seems to have worked!

no more stacktraces, though what I’m actually rending looks like crap. but at least that’s something I can fix! 🙂

primo 🙂

hah, well good

@alex-dixon I think its great that someone is taking this on. In my view, create-react-app does a lot of things to reduce pain, but the main thing it did was to get babel and webpack working together with no configuration and sensible defaults. The reality is that there is nothing even remotely as painful as that in the cljs ecosystem (that I have found). Dan has suggested twitter that he’s not necessarily even that wedded to zero-config as an absolute. I think it was just a way to pull all community members together to force a decision on things. I also think they worked to fix the underlying tools in some cases. Somethings I really like about c-r-a: (1) somehow it coaxes beautifully formatted messages out of the compiler and clears the screen between every file change. My cljs tool chain will spit a stacktrace at me for something as simple as a missing dependency. Assistance with dependencies would be so nice (e.g. collect all the available packages and then do an edit distance calculation with the missing dependency to suggest the nearest once so that people can see if they uses a / where a . should have gone or just typoed). (2) Getting a repl to the browser was really hard. I just don’t use it because I don’t get whats going on. (3) The c-r-a development server comes configured to deliver the frontend bundle on any GET to any URL. With a single line of config, you can make it proxy non text/html requests to your api server. (4) c-r-a installs best-practice linting and debugging tools. I’ve seen people here in slack recommend tools that will help with stacktraces by only showing the lines in your code. (5) the c-r-a readme is an incredible resource and gives one confidence that it is possible to develop and app using c-r-a and then deploy it in the real world. A similar one would be a great opportunity to explain the practicalities of the clojure universe that I’ve only absorbed by spending time here on slack (e.g. the fact that a well-maintained 7 year old library might still have a version like 0.24.1).