luminus

romain 2019-06-20T06:32:00.037300Z

@rnandan273 I might give you some informations https://shadow-cljs.github.io/docs/UsersGuide.html#_build_tool_integration

romain 2019-06-20T06:32:08.037600Z

At the caution section

rnandan273 2019-06-20T06:41:20.038Z

@romain Thanks, will check

rnandan273 2019-06-20T06:43:20.039200Z

@romain Using lein shadown would have meant using shadow-cljs.edn info in project.clj, here i have to maintain both

eskemojoe007 2019-06-20T12:56:21.040Z

@yogthos Is the pragmatic bookstore errata the best place to submit bugs and errors we see in the current beta version? Or would you rather some git repo, etc?

yogthos 2019-06-21T12:25:51.045100Z

the forums uses to support their own custom markdown that used ~~~ instead of the triple backtick

romain 2019-06-20T12:56:47.040500Z

@david.folkner I want nothing, I'm not the author ^^'

eskemojoe007 2019-06-20T12:57:03.041Z

I realized that as I pressed enter...whoops.

romain 2019-06-20T12:57:08.041300Z

😛

romain 2019-06-20T12:57:30.041800Z

But yes I think it's better to use pragmatic for that

yogthos 2019-06-20T12:58:40.041900Z

Hi, yeah that's the best spot, that way we can track it all in one place

yogthos 2019-06-20T12:59:34.042100Z

There's no real difference, all lein-shadow does is allow you to keep the shadow config in project.clj

yogthos 2019-06-20T12:59:51.042300Z

so if shadow runs standalone, I'd just go with that

yogthos 2019-06-20T13:00:52.042500Z

👍

eskemojoe007 2019-06-20T13:00:55.042700Z

I just hate that it doesn't seem to have any code formatting. But I'll keep posting some basic stuff there.