Clojurians Log v2

yes it works ok and I have the warning as well

can cut a release happily now

@richiardiandrea: nice! thanks 🦜 some more currency 😉

thank you for the patch!

@superstructor: 0.1.1 should be on Clojars

@richiardiandrea: thanks will test now. Also did you know you can do this in your build.boot to pass config to devtools ?

(task-options! cljs {:compiler-options {:external-config {:devtools/config {:features-to-install [:formatters :hints :async]}}}}

now I know 🙂

and I was trying to pass option through the task but it does not work and I don't know why

for instance :dirac-opts {:log-level "DEBUG"} does not work

@richiardiandrea: devtools gets the config from the compiler options external config here: https://github.com/binaryage/cljs-devtools/blob/master/src/lib/devtools/preload.clj

used to be called :tooling-config but thats deprecated.

yeah, that above is more of a dirac option, which should work as I am passing it to dirac/boot!

yeah I don’t think dirac supports external-config / tooling-config yet as searching the dirac source does not find those strings (except in project.clj in relation to passing config to devtools)

@richiardiandrea: devtools config options: https://github.com/binaryage/cljs-devtools/blob/master/src/lib/devtools/defaults.cljs

I’ve added a commit discussing using RELEASE versions for dirac: https://github.com/binaryage/dirac/commit/a15a8d2ddf1d61d1ddfe58dc67b3057a528915e9?short_path=11d8910#diff-11d8910b58f5c70ccb3bedc0f37c892f

Would be interested in feedback if people think this is a bad idea

I can’t see too many downsides considering that you can’t use dirac if chrome plugin and lein dep aren’t in sync anyway

@superstructor: if you feel very open-sourcy today, a PR to the readme with the way you can configure devtools like the above would be incredibly useful!

@richiardiandrea: ok will do

@danielcompton: some people don’t use lein dep, we use boot, so what does lein dep being in sync mean please for those of us ignorant of lein ? :thinking_face:

I think he means if the version is not in sync, it happens in boot as well

In boot I guess we could write a task that checks the version of the Chrome extension and sets the version of the dep accordingly

This would actually be perfect for our new powerlaces/boot-cljs-devtools ;)

I estimate that the task would just parse some json in Chrome (maybe Darwin can help here)

Just updated the docs to remove all references to lein

There is nothing lein specific about the install instructions

AFAIK Boot will also download the latests version when you specify RELEASE

@richiardiandrea: I guess you could write a plugin, but seems like a lot of work when you can just get the deps to update automatically

@richiardiandrea: is it possible to use boot-cljs-devtools without dirac?

It seems the namespace requires dirac so removing the dep would break it

@martinklepsch: not familiar with boot-cljs-devtools, but you could work-around it by creating empty dirac namespace in your project (and maybe implementing empty install! function there)

but agree that this should be addressed, most people won’t use dirac

@darwin: really, why wouldn’t most people use dirac ? its awesome.

it is an advanced tool, relatively difficult to setup and keep maintained - most people don’t need that power ATM, I think

@martinklepsch: not at the moment, and I don't think a task for cljs-devtools would be valuable..it is so easy to add it to an existing code base...a task is a bit overkill.

Dirac on the other had needs to have nrepl server running and some conf, so that is why a task makes sense

In lambone boot dev launches the normal boot-cljs-repl and boot dev -d launches dirac nrepl (they are mutually exclusive)

@richiardiandrea: what about renaming the task to boot-dirac or something like that?

@darwin: yeah not a bad idea definitely, but it includes both 🙂

cljs-devtools is pre-requisity for dirac, but not vice versa

so naming it “dirac” would make sense even if it includes cljs-devtools

technically dirac does not require cljs-devtools, but I expect everyone using dirac to use cljs-devtools as well

uhm understand

makes sense yeah

yeah I think it makes sense to call it boot-dirac and focus on that use case of devtools+dirac together only, devtools alone is easy to add as a dep + :compiler-options :preloads, don’t really need a task for devtools without dirac.

@richiardiandrea: 👍 Good stuff, hope you don't mind my unsolicited opinions 🙂

@martinklepsch: absolutely not! it makes the experience better so that's all good 😄

I wasn't aware things have become that easy with :preloads, that's amazing! (I thought you still need a separate namespace that you require in dev only and stuff)

well I think the thing here is that @darwin

awesomely added it for us

with cljs-devtools.preload

@martinklepsch: no, you don’t need a namespace

@richiardiandrea: please don't make dirac too easy to setup. I'm not able to handle support requests from newbies getting dirac "for free" via some automated task 😉

btw. guys, dirac.preload will be a thing in next release (soon-ish), so dirac setup should get easier, but I still see value in those boot tasks, they can be trivial and maybe ease upgrading process in future if I decided to change the setup anyhow

ah ah it is actually a collective effort so we'll try to slack a bit 😄

but I know what you mean, I saw that figwheel is exploding with feedback 😉

exactly bhauman is super-nice guy, so it eats a lot of his time to support people, I can imagine

oh yes he is, a lot of people here are actually

🌈

passionate about their work is probably the right word here

good night folks 👋 lovely being here 🙂

lol

we are missing the unicorn icon