This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-27
Channels
- # alda (21)
- # announcements (7)
- # beginners (70)
- # boot (95)
- # braid-chat (28)
- # bristol-clojurians (2)
- # cider (22)
- # clara (4)
- # cljsjs (13)
- # cljsrn (40)
- # clojure (93)
- # clojure-argentina (1)
- # clojure-art (1)
- # clojure-miami (3)
- # clojure-norway (1)
- # clojure-portugal (2)
- # clojure-russia (39)
- # clojure-sg (3)
- # clojurescript (25)
- # clojurian-chat-app (4)
- # community-development (5)
- # conf-proposals (20)
- # cursive (48)
- # datomic (39)
- # devcards (5)
- # dirac (4)
- # editors (2)
- # events (11)
- # funcool (65)
- # hoplon (95)
- # jobs (12)
- # ldnclj (4)
- # lein-figwheel (2)
- # leiningen (1)
- # om (311)
- # onyx (20)
- # philosophy (4)
- # proton (41)
- # re-frame (83)
- # reagent (49)
- # ring-swagger (3)
- # spacemacs (8)
- # yada (5)
a question is there any known problem in executing sifts one after another?
Like (sift :add-meta) (sift :add-jar) ?
@richiardiandrea: haven't heard of any myself
Quick question - are [str]
and #{str}
argument types equivalent? It seems that when I have #{str}
in a task it accepts either of #{"something"}
and ["something"]
.
@jaen, @gadfly361: Hey so far I’ve been calling semantic-UI through cdn like this:
[:link {:rel "stylesheet" :href ""}]
[:script {:src ""}]
[:script {:src "}]
Do you guys have any experience with the recommended way of building it with gulp? I’m not sure how to place it in my boot project and where to include it.@jaen: with opt = [str]
-> boot task --opt "x" --opt "x"
-> opt = ["x" "x"]
with a set it'd be #{"x"}
at least thats what I'd expect. I believe you can pass both because they're coerced in a way
(all guessing / not tested)
@martinklepsch: I'm saying wrt. build.boot
, not command-line options, I figured that maybe coercions like that happens before options to a task are passed so #{str}
will expect #{"something"}
, but it also makes sense for the task to coerce vector to a set when called. And at least it seems to be the case, as I can call a #{str}
options with both ["something"]
and #{"something"}
, so our guess is probably correct, but wanted to know if it's meant to work like that, or a bug.
Ah, then I'm not sure if I can help you - I use semantic-ui's SASS port through boot-middleman
.
so in that case, there is no way to do things like set the semantic global primary colors and such?
But you could probably make a directory for assets, use their build system to output CSS to a subdirector resources
and then just have a boot task run gulp when things change in the assets directory.
Semantic-ui's theming method is incompatible with SASS, since it requires interpolation in imports and from what I read of the issue SASS doesn't want to do that
Something like this:
project/
├── build.boot
├── resources
│ └── output-of-semantic-gulp
└── semantic/$run-gulp-in-here
?Yeah, something like this - semantic
would be where you would have your source files like your theme our custom less files and you would configure it to output to some directory in resources
, for example resources/public/assets/stylesheets
or something like that.
Looking at - http://semantic-ui.com/introduction/build-tools.html#semanticjson - the directories seem to be configurable.
@richiardiandrea: no problems known to me
Has anyone seen the following error when attempting to start a cljs-repl from within a boot repl? Sequence of commands:
> boot repl
Now within the boot repl:
> boot.user=> (start-repl)
Results in this:
java.lang.IllegalStateException: Can't change/establish root binding of: *cljs-repl-env* with set
Hmm, boot-test is getting slower and slower for me in one project. When started it takes 10s to run tests but after about 20 runs it takes 25s. I though at first it was leaking pods but pods were garbage collected after some time.
I'm writing a boot criterium task - now thinking what would be the best API to provide in a task like (bench)
. Currently I have the following:
(deftask bench
[g goal GOAL sym "qualified name of the goal function to run"
a args KEY=VAL edn "map of arguments passed to the goal function"
c criterium-opts KEY=VAL edn "options to the Criterium"
P progress bool "show progress report?"
Q quick bool "run a quick benchmark?"]
...)
and also supporting a case when you want to bench the same fn with different versions of dependencies
I am hacking sift
and there is something I cannot figure out, basically when I call (sift --option) (sift --option)
the first (fn [fileset] ...)
is not executed
I tried by putting println inside 😄
I am in a deftask
and I will try more and maybe have a little repro case
if the are chained (sift --option1 ... --option2 ...)
in the same sift
no problem
@richiardiandrea: i'm no expert but I think that makes sense. the fileset is a value and if you haven't commit! ed after the first sift, the second sift is probably sifting the as yet unmodified fileset
@raywillig: I was not thinking about that, but it makes total sense!
Sift task calls commit! before calling next task
there is a problem then
@micha - if you have any spare time, would be great if you could advise on https://clojurians.slack.com/archives/boot/p1453920747000550
I'm trying https://github.com/adzerk-oss/boot-cljs/wiki/Example but main.js is not saved to ./target
I notice this: :output-dir "/Users/ion/.boot/cache/tmp/Users/ion/bootcljstest/48m/pj5f4p/main.out"
Which makes me wonder if the wiki page I'm following is out of date -- perhaps there is another necessary option
ion: if you have set BOOT_EMIT_TARGET=no
you need to use target
task
@juhoteperi: ok, yes, I have that environment setting, as recommended by boot "Implicit target dir is deprecated, please use the target task instead."
I updated the wiki page
Yes, boot cljs -s -- target
works for me. The --
separates boot subcommands -- that's what I remember from a boot video, but I'm curious if that arises from boot directly or if it is a shell parsing thing
--
is not necessary, it can be used to make it easier to understand the command
Not sure if that is documented on Boot wiki. Should probably be.
is there a way to access tmpfiles (the whole record) without passing by (with-pre-wrap [fs]
?
Hey guys, I’m recently getting this (non-fatal) error on my cljs builds,
java.util.concurrent.ExecutionException: java.nio.file.NoSuchFileException: target/js/main.out/cljs_deps.js
java.nio.file.NoSuchFileException: target/js/main.out/cljs_deps.js
What is it that needs this file, and where’s the first place I should be looking to fix this error? ThanksTo be more accurate, it doesn’t happen when I first build, but as I’m iterating and interacting with the app a bit, I’ll look back and see that for the last n cljs-builds this error was there
Ever since warnings about BOOT_EMIT_TARGET=no
started cropping up, I can’t get a cljs-repl to work. I am using the target
task and I have a boot.properties
file with a BOOT_EMIT_TARGET=no
line in it, but I still get the warnings and I am getting a no such file exception whenever I try to start the cljs repl. Anyone know of anything obvious I may be missing that could explain this?
@chris-andrews: Which OS?
I’m on OS X
My normal flow is to start a boot cljs and cljs-repl task, and then boot repl -c
to start the cljs repl. I just noticed that when I connect using the repl my target
directory gets emptied
I was also having some problems when I would change a cljs file, but they seem to have gone away except when I try to connect the repl
If boot repl
and then make a change and save the file, I think I get the same type of message
Ok, not sure where the 2.4.2 issue was coming from, but I got that working. So I only encounter these problems on 2.5.x
@micha: we were talking long time ago about clojure test and the fact that you don't have boot
core required...so how can I require it in a clojure.test
basically? In a pod?
My error is the classic:
Caused by: java.lang.IllegalArgumentException: No implementation of method: :-mk! of protocol: #'boot.tmpregistry/ITmpRegistry found for class: nil
(I am trying to revive boot's tests, I can't live with the fear of breaking stuff :D)
Another way to say this is, is there a way to initialize the boot core stuff so that I can put it in a fixture
?
About above above I guess you cannot do (sift --) (sift --)
in a task but (comp (sift --) (sift --))
I cannot call (core/init!)
as I am missing the pod initialization...and worker pod, which are passed to -main
...digging digging
@richiardiandrea: you can't really do that i don't think
@micha can you expand a bit on that?
if was trying to create a pod with boot.core
inside but it does not look it's going to work
returns a weird java.lang.IllegalStateException: Pop without matching push
let me try
the issue arises because with-eval-in swaps out the clojure thread local bindings stuff
understand, I will maybe push something at the end of (my) day and you can have a look, but now it looks like something is working