This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-04
Channels
- # admin-announcements (6)
- # alda (1)
- # announcements (3)
- # aws (4)
- # beginners (233)
- # boot (82)
- # cider (11)
- # cljsjs (21)
- # cljsrn (7)
- # clojure (262)
- # clojure-japan (1)
- # clojure-russia (129)
- # clojure-sg (2)
- # clojure-taiwan (2)
- # clojurecup (23)
- # clojurescript (162)
- # clojurex (3)
- # core-async (18)
- # cursive (81)
- # datavis (183)
- # datomic (23)
- # emacs (2)
- # funcool (25)
- # ldnclj (82)
- # lein-figwheel (3)
- # om (196)
- # onyx (74)
- # parinfer (7)
- # portland-or (12)
- # re-frame (60)
- # reagent (48)
- # slack-help (1)
- # yada (9)
@lukemorton: I suggest asking in #C03S1L9DN this isn’t really specific to Boot
^^ I want a boot specific solution
maybe still better for #C03S1L9DN tho
@lukemorton: then I might not understand the question: you were asking how to run cljs test from within a cljs repl right?
so I tried using boot-cljs +test via tenzing and just couldnt get anything working, looks like doo and running on nodejs is still in development/not working
so thought to ask if there is an easy way to just run this via a browser repl?
without needing any other js runtime
@lukemorton: tenzing ships with an old boot-cljs-test version
try 0.2.0-SNAPSHOT
works for me in a newly generated project
that using phantomjs or node?
phantom
for just running tests in a repl I’d suggest trying run-tests just as in clojure, not sure if that will just work though
@gary: sorry but we're full
re: clojurecup
Hint: I don't think Clojurecup's rules (explicitly) forbid bribing judges 😄
hahahaha
@juhoteperi: i have been thinking about the GPG stuff a lot the past week
Yeah looks okay
I wouldn't expose a multimethod directly, maybe instead just provide function to register configure calls and keep them on a atom
I just think that it's better to expose a function instead of multimethod
It is easier to change the implementation later if it's a function
Perhaps multimethod is fine
Or we could hide the multimethod behind a macro, I'm just thinking about the API we want to expose
Could be useful for setting configuration that should be used for deploy and download
But I'm not sure if that would be the best solution for that
(configure-repository
{:url #""
:ops #{:deploy :resolve-dependencies}
:fn (fn [base] (merge base {:username "bar" :password "foo"}))})
How about something like that?
Will probably make sense to allow regexes for urls
I dunno 😄
Maybe not
We should implement the multimethod version and see if works
Using boot-cljs, I’m not able to get the compiled javascript file to go where I want it to using cljs compiler options. Here’s my task
(deftask build []
(comp
(speak)
(cljs :compiler-options {:output-to "index.ios.js"
:optimizations :advanced})))
that works and creates a file with correct name. But is there a way to have that file end up outside of the target
directory the project root?
right now the file ends up in ~/project-root/target/index.ios.js
but I want it in ~/project-root/index.ios.js
(deftask copy
[f from PATH str "source"
t to PATH str "destination"]
(with-pre-wrap [fs]
(io/copy (tmp-file (first (by-path [from] (output-files fs)))) (io/file to))
fs))
@micha Thanks! Unfortunately for me I didn’t look back at your code to see you edited and added the first
call. But I poked around in the repl and figured out what was wrong. It was a boot learning experience for me, so I’m better off anyway
@micha: @alandipert Good luck with the ClojureCup!
@martinklepsch: Oh, you're participating too. Good luck!
Yes! How about you @danielsz?