This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-12
Channels
- # aws (21)
- # aws-lambda (8)
- # beginners (53)
- # boot (56)
- # braveandtrue (1)
- # cider (49)
- # cljs-dev (8)
- # cljsjs (1)
- # cljsrn (57)
- # clojure (403)
- # clojure-austin (17)
- # clojure-dusseldorf (10)
- # clojure-greece (9)
- # clojure-spec (57)
- # clojure-uk (144)
- # clojurescript (60)
- # datomic (149)
- # docker (1)
- # emacs (1)
- # hoplon (23)
- # humor (1)
- # jobs (1)
- # leiningen (2)
- # luminus (1)
- # off-topic (1)
- # om (24)
- # om-next (15)
- # onyx (23)
- # protorepl (2)
- # re-frame (58)
- # reagent (90)
- # remote-jobs (1)
- # ring-swagger (4)
- # slackpocalypse (1)
- # spacemacs (2)
- # specter (18)
- # untangled (4)
- # vim (1)
- # yada (27)
to the above, i tried with the boot.pod/resources fn but that returns an url and dont know exactly what to do with it
for example (io/file (boot.pod/resources “cljsjs/babel-polyfill/development/polyfill.inc.js”))
throws an error … any other suggestions?
@michael.heuberger boot sift -j
can be useful for what I understood. You can do boot sift -h
for help on the sift task.
@mynomoto thanks but not sure what parameters to use
how do i copy the above with sift to the fileset?
The sift task will add things to the fileset, in the -j
case it will add things from jars to the fileset.
right, I was just updating readme for our project and it got me thinking, why I never have to do this 😉
@michael.heuberger boot -BPd cljsjs/async:2.0.0-rc.4-0 sift -j 'cljsjs/async:development/.*\.inc\.js$' show -f
is an example that micha posted some days ago.
ah, thanks!
Hey all - any options for disabling cert validation in boot?
@mattyulrich i think you'd have to do that at the JVM layer
I see my github comment was posted here, but I’ll ask again anyway - I’m trying to add tests to boot. The function I’m trying to test is in boot/pod/src/boot/tmpdir.clj
, and so I’m adding the tests in boot/pod/test/boot/tmpdir_test.clj
. However, make test
does not seem to run any of the tests in boot/pod/test
, and I don’t see an obvious way to make it happen. Any tips?
@bhagany the king of all things test is @richiardiandrea but i can have a look when i get into the office this morning
Thanks Micha - I’ll see if I can find a good way to do this in the launch4j config.
@bhagany do you want to test the fileset?
I’m creating some filesets with map->TmpFileSet
, but I don’t really need it run in a task
Ok lemme check then, it should be easy, probably the dir is not on the clrsspath
Uhm it looks like we have other tests in that folder
Ok it has been commented out: https://github.com/boot-clj/boot/blob/master/Makefile#L99
Maybe @micha can help here 😁
In theory also boot test should work, like the line above that one
I have a question, is there a reason why we can about time when using boot.core/fileset-diff
? I am looking at boot-reload
with figwheel again and I don't see any reason not to just use :hash
...but maybe I am missing something
I switched to just :hash
in Perun, because :time
would change for reasons I couldn’t determine in between watch
loops
@bhagany maybe it has something to do with your patch because here https://github.com/boot-clj/boot/blob/2.6.0/boot/pod/src/boot/tmpdir.clj#L205
it is basically creating a nested data structure
and then diffing
(I mean your patch could fix that)
which is nested, but the part that needs to be nested to be affected by my patch are the values in the inner-most map (aka ”xxx”
and 1234
)
oh right
It is weird because I have two files with exactly identical content and they have different :hash
key
then again, I’m not sure how :hash
is calculated… maybe it takes the file name into account?
looks like this one: https://github.com/arichiardi/boot/blob/commit-verbosity-inc/boot/pod/src/boot/tmpdir.clj#L97
if I am looking at the correct place 😄
yeah, I think you are. following on from there, https://github.com/arichiardi/boot/blob/commit-verbosity-inc/boot/pod/src/boot/from/digest.clj#L62, it looks like it’s just using the file contents
I will open an issue with what I found