This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-28
Channels
- # admin-announcements (4)
- # beginners (11)
- # boot (148)
- # cider (74)
- # cljs-dev (31)
- # cljsrn (30)
- # clojure (55)
- # clojure-berlin (15)
- # clojure-greece (1)
- # clojure-japan (18)
- # clojure-poland (35)
- # clojure-russia (72)
- # clojure-spec (35)
- # clojure-uk (34)
- # clojurescript (134)
- # cursive (26)
- # datomic (42)
- # dirac (7)
- # editors-rus (1)
- # emacs (17)
- # hoplon (29)
- # jobs-rus (3)
- # juxt (1)
- # luminus (11)
- # off-topic (9)
- # om (66)
- # onyx (49)
- # pedestal (1)
- # perun (19)
- # proton (13)
- # protorepl (5)
- # re-frame (31)
- # reagent (13)
- # ring (2)
- # spacemacs (1)
- # specter (40)
- # spirituality-ethics (2)
- # test-check (41)
- # untangled (7)
- # yada (17)
I assume I'm running into this: https://github.com/adzerk-oss/boot-cljs-repl/issues/44
@escherize: I'm using 93, but I don't use the repl
@timothypratley changing to [org.clojure/clojurescript "1.9.76"]
fixes that issue. I'm still not sure if i'll get bit by something though
🙂 yeah upgrades are a vicious cycle lol
@escherize: are you asking about repl or boot-cljs? There are known issues with 93 & source maps
Generally boot-cljs and cljs versions don't have to match
I was having trouble getting (a project started from tenzing that's changed a bit) working with new deps.
That's great news, @martinklepsch - I was worried I'd get hamstrung by a version mismatch somewhere.
93 build is not even a proper release, 89 should work fine
And the problem should be fixed in later version, I've been testing current master (146) with Boot-cljs and it works fine
@juhoteperi: right, the issue is that when you do boot show --updates
it shows you 93 and I think that's how people end up with it 🙂
I don't know, release early and often, no? You upgrade, things don't work, you downgrade 😛
Hmm, 93 isn't a stable release. But there's no indication of this in the version name
right, the differentiation between stable/unstable aside
I wonder if that bug was known at the time of release and if it would have been discovered during pre-(stable)-release testing
I think my concern is that I've seen a lot of people upgrade to .93, not realising it's an unstable release. Then stuff breaks for them. And they're confused as to why.
Yeah, I guess my "You upgrade, things don't work, you downgrade" is a bit ignorant, usually people don't just downgrade but try to see what breaks. Guess I'll take it back 🙂
@borkdude: boot -d some/dependency:0.1.0 repl
(IIRC about what lein try does)
I'm maybe asking too much, but is it also possible to have (require '[clj-time.core :as t])
executed when I call boot -d clj-time repl
? 🙂 It could be a useful script to have when I want to do some ad hoc date calculations
@borkdude: like this?
boot -d clj-time repl -e "(require '[clj-time.core :as t])"
@borkdude: these are the docs for boot itself. Tasks like repl
have separate docs which can be found via boot $task --help
You're welcome 🙂
My goal is to have show -c
output the classpath I need to load cljs-time
with planck
it's boot -d com.andrewmcveigh/cljs-time:"0.4.0"
the boot option to recall a string will be in the next release also, there's already a ticket open for it
is there a way to concatinate files with boot? I don't see anything in boot sift -h
or boot -h
... should I write a task that slurps and spits?
@timothypratley: nothing built in unfortunately
we should start a boot-contrib project that hosts a bunch of community maintained tasks (all using pods ofc)
🙂 ok makes sense.
Has anyone succeeded in using boot-cljs-test
to run async tests?
I’m currently unsure if I’m experiencing a Doo problem or a boot-cljs-test
problem
hrm. Seems to have been just PEBKAC
@anmonteiro: I did with promises, the code in replumb shows how to, but i have a pretty huge macro for it...
@richiardiandrea: it was quite easy after all:
(deftest test-foo
(async done
(take! (my-function-that-returns-a-channel)
(fn [_]
(is false)
(done)))))
boot-cljs-test
uses doo
under the hood which already has a reporter for end-run-tests
ah ok I thought that didn't work for you
also, check clojurescript's test suite (which uses a similar thing just named latch
)
@richiardiandrea: will do. the actual problem was that async
must be the last thing you return from deftest
and I wasn’t doing that 😄
latch
looks cool
for future reference / interested folks: https://github.com/clojure/clojurescript/blob/053d7f1ead6698b38e7ff656e0910ebc8bb8f729/src/test/self/self_host/test.cljs#L12
I used a promise because of that now that I think about it
a promise is infinitely nestable so no counting is necessary
So I had this idea of putting boot-cljs-devtools
in a place where it is easy for anyone jumping in to release on clojars, I am willing to maintain it, but I also, after Martin's suggestion, don't want to keep it under my own name for two reasons: 1) it was not my work and I don't want to take all the credit 2) it is good for others to be able to release on clojars if necessary.
So I was wondering if boot-clj
can be a good place for putting this, of if there is another "umbrella group" we can use for this and maybe for boot-contrib
(project with boot indipendent tasks)
i think boot-clj is a good umbrella group, and we can make teams etc
yeah I was thinking that too 😄 so I'd probably just need access to my user (`arichiardi`) so that I can deploy using that group, then I will fork boot-cljs-devtools
(I asked Jupl, the owner, and he is fine with it) and change that as well
awesome thanks Martin
@richiardiandrea: I added you. Let me know if there's anything else to do 👍
yes, on clojars
ok so boot itself is boot/*
I feel like another group might be good just to keep things slightly distinguished
Also I'm not in that group so I can't add anyone (and it seems good to keep clojars-push access for boot itself limited)
I like bootlaces
for instance, as group name as well
oh I have just seen that it has another group name ..
could be confusing, although I really like the pun 😄
yeah me too
you have more fantasy then me for sure Marting (see re-frame logo), let's come up with a name 😄
boot-other
boring
well I was just going to say boot-contrib
but I guess that doesn't have a lot of fantasy 😄
yeah that was my original idea as well, it kind of makes sense
boot-spurs ? 🙂
is there a name for the shoes from back to the future? 😄
oh that's a good one...let me check
they were Nike
self-lacing boots I found, self-tying
self-tying-boots-by-nike/boot-cljs-devtools
I think we found the winner!
power-laces
-> https://www.engadget.com/2015/10/21/nike-mags-back-to-the-future-shoes-2016/
power-laces/boot-cljs-devtools
that seems cool
yay, nay?
man, you cannot vote the + AND - at the same time 😄
yeezy-boots
it's so other people can click haha
yeezy, I am looking it up
kanye west reference, and definitely joking
lol I saw that 😄
american rapper who also makes weird shoes http://cms.myspacecdn.com/cms/x/15/7/adidas-yeezy-boost-1300.jpg
boot-buckles
?
marketing video: https://vimeo.com/124999974 😄
@alandipert: are these pockets on shoes? haha
haha yes, to store your clj/s quickref card
@alandipert: @micha btw, will any of you join ClojuTRE/EuroClojure this year?
soooo.... 😄
@martinklepsch: i think your poll up there has a winner?
@richiardiandrea: sure, you might want to consider powerlaces
vs. power-laces
, it's not correct but looks nicer imho 😄
yeah but we have bootlaces
one word right
powerlaces/boot-cljs-devtools
not that bad either
so ok, now i just need my arichiardi
user to be in the boot-clj
group on clojars and I guess we are done 😉
@richiardiandrea: it is done
awesome
@martinklepsch: sadly no 😢
there's no boot-clj group on clojasr
err yeah, the group is boot
@richiardiandrea: what do you want to do with the boot group?
yeah i see boot
i thought we could create subgroups lol
oh yeah, maybe better to have powerlaces clojars group?
I'll do it
I thought we decided it's good to keep that group (boot) to "core" stuff so we can be very liberal in adding people (to powerlaces)
yes no it's my fault 😄
I just need to push with the correct group do I?
That sentence above makes no sense but I guess you get the idea 😄
Hmm, is boot-cljs-devtools just an example or are you making such task?
I'm trying to make this (second code example) https://github.com/torgeir/boot-protobuf#usage compile my protobuf-file. It seems it needs protobuf-java-3.0.0-beta-4.jar on the classpath for this to work. If I do boot -s protobuf-java-3.0.0-beta-4.jar my-task
it works (when my-task
has the contents of the second code example). However, adding [com.google.protobuf/protobuf-java "3.0.0-beta-4”]
to boot with set-env!
under :dependencies
and running my-task
does not work. Ideas on how to make boot/javac pick up the dependency inside my task?
@juhoteperi: it is an actual task jupl developed for including both cljs-devtools and dirac