This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # architecture (25)
- # bangalore-clj (1)
- # beginners (21)
- # boot (45)
- # cljs-dev (38)
- # clojure (272)
- # clojure-austin (7)
- # clojure-finland (7)
- # clojure-france (3)
- # clojure-italy (7)
- # clojure-japan (1)
- # clojure-russia (13)
- # clojure-spec (36)
- # clojure-uk (31)
- # clojurescript (96)
- # core-async (15)
- # cursive (16)
- # datascript (3)
- # datomic (97)
- # emacs (107)
- # hoplon (16)
- # jobs (9)
- # keechma (1)
- # luminus (1)
- # off-topic (19)
- # om (39)
- # onyx (15)
- # pedestal (3)
- # planck (22)
- # protorepl (4)
- # re-frame (20)
- # reagent (3)
- # ring-swagger (25)
- # specter (26)
- # test-check (19)
- # testing (1)
- # untangled (381)
I’m trying to set up boot-cljs-test with fixtures, i.e files containing test data and reference output, and then generate a test case for each file found in the fixtures diretory. however, I haven’t found a possibility to get those files into the test build. I tried adding them as a resource to the fileset, anything I’m overlooking?
(deftask backend-test (merge-env! :source-paths ["clj/backend/env/test" "clj/backend/src" "clj/backend/test"] :resource-paths ["clj/backend/fixtures"]) (test-cljs :js-env :node :exit? true))
as far as I can tell from https://github.com/crisptrutski/boot-cljs-test/blob/master/src/crisptrutski/boot_cljs_test.clj it looks like stuff like node_modules is copied manually into a temp dir
@micha ok, looks I’m missing something here, as I just try to get the directory relative to the current working directory
in general i think you want to use the classpath rather than the filesystem when you access things
then your code will work the same way if the file is in the filesystem or in a jar or even downloaded from a URL
hmm, but i’m in cljs land, so my tests execute in a nodejs env, so I guess I’m out of the jvm land here
I’m using https://github.com/pkpkpk/cljs-node-io for accessing the filesystem right now
The leiningen repl colorizes and pretty-prints its output by default. How do I get this in a boot repl?
When I start the repl 'boot repl' I get the following: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. nREPL server started on port 44977 on host 127.0.0.1 - <nrepl://127.0.0.1:44977> I added https://github.com/adzerk-oss/boot-logservice and now I get INFO boot.user - wow SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. So, the logservice seems to be working but the SLF4J messages remain. How do I get rid of them?
i looked at the Puget and Whidbey projects but i couldn't really unwind the leiningen stuff it was doing
that error means it can't find slf4j on the classpath (no slf4j dependency in your project)
the URL printed in the message will show you what you need to do to get rid of the message
@mobileink What is html import?
Hi all. How does one determine path of downloaded jars after “boot dev” has been invoked?
@gamecubate they will be in your local maven repo
Yes thanks @micha Found it.
@juhoteperi see https://w3c.github.io/webcomponents/spec/imports/ and https://www.html5rocks.com/en/tutorials/webcomponents/imports/ (possibly a little outdated).
@mobileink Not supported currently
@mobileink I guess it would be possible to support that, currently Boot-reload will do page reload if the currently open html file is reloaded, but if the changed html file is different one, Boot-reload could check if there is import link to the file, similar how CSS reload works: https://github.com/adzerk-oss/boot-reload/blob/master/src/adzerk/boot_reload/reload.cljs#L63
juhoteperi: well, fyi my thing did start reloading the html, but it seems to reload the entire page, whereas what i would like is to just reload the imported bit. the bits being polymer components, fwiw. i'm not sure there's a way around this currently. once you register a webcomponent, there's no way to un/reload it - you get an "already registered" exception if you try.
I wonder if Figwheel handles this
I'm pretty sure it doesn't. I don't think it looks at changed html files at all.
If it does, for me it is quick to throw an event, but I haven't seen it
Oh got it