This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-30
Channels
- # admin-announcements (4)
- # alda (49)
- # beginners (42)
- # boot (55)
- # cider (33)
- # cljs-dev (4)
- # cljsjs (3)
- # cljsrn (152)
- # clojure (92)
- # clojure-belgium (3)
- # clojure-brasil (18)
- # clojure-dusseldorf (32)
- # clojure-france (2)
- # clojure-greece (10)
- # clojure-japan (1)
- # clojure-mexico (1)
- # clojure-russia (50)
- # clojure-sg (1)
- # clojure-spain (1)
- # clojure-spec (12)
- # clojurescript (262)
- # core-async (2)
- # cursive (7)
- # datomic (79)
- # emacs (16)
- # euroclojure (2)
- # events (1)
- # hoplon (260)
- # jobs (2)
- # jobs-discuss (1)
- # keechma (7)
- # luminus (8)
- # mount (7)
- # off-topic (3)
- # om (101)
- # onyx (33)
- # re-frame (34)
- # reagent (10)
- # slack-help (4)
@onetom: yeah, that's what I'm thinking. Also for boot task -h
but boot -h
seems more helpful specially when there are some :refer :all
on build.boot
@juhoteperi: sure, I remember listening on a random port with boot-http was an issue for me at the beginning.
With Datomic however I can have a singleton connection and fork it further for the individual tests with the datomock
lib
and thanks for confirming my worries!
im trying to use this new boot-maven-interop
approach, so
1. there is only a single source of truth about the dependencies
2. intellij understands where those dependencies are and provides code navigation
3. i have autocompletion for specifying dependencies
this all works but then how can i get a repl?
if i start boot repl
i get .nrepl-port
file but to utilize it i would need to create a Remote REPL
in IntelliJ with the Use Leiningen REPL port
option.
it doesn't seem to work however, because I don't have a project.clj
... 😕
ok, i tried it on a "from scratch" project and it worked there... 😕 the problem was probably not specifying clojure as an explicit dependency
@onetom: Boot-alt-test has option to disable parallel tests
sure, it was just confusing that boot repl
worked but couldn't connect to it from intellij...
although that was not the problem at the end, but we couldn't track it down what it was exactly. just recreated the intellij project and it was okay then...
does anyone know how to get foundation sass to work with boot-sass? Adding [org.webjars.bower/foundation-sites "6.2.1"]
to my depenencies doesn't give me any errors other than an empty css file with foundation comments at the top when I do @import "foundation-sites/scss/foundation"
@lucien.knechtli: you may need to use the sift
task to dump that dependency into the fileset
i'm not sure but it may be that they need to be files on disk rather than jar resources on the classpath for the sass compiler to pick them up
according to boot-sass, it should pick it up from the jar resources
Resource META-INF/resources/webjars/{package}/{version}/{path} can be referred using {package}/{path}
E.g. bootstrap/scss/bootstrap.scss => META-INF/resources/webjars/bootstrap/4.0.0-alpha/scss/bootstrap.scss
on the githubsee the -j,--add-jar
option (do boot sift -h
at the command line or (doc sift)
at the repl
and it seems to be, to a limited extent. the compiled css file has comments from foundation.scss
it just doesn't seem to be importing anything from the files that foundation.scss imports
when I put the actual sass file structure with my sass files, then I get a bunch of errors that look like it isn't processing relative references
for ex: in util/util.scss, @import 'unit';
says it can't find unit
, which is in util/unit.scss
no dependency conflicts
that's in foundation's sass code though
shouldn't need to modify that..
Loading order for @import "{name}"; on file at {path}
Local file at {path}/{name}.sass or {path}/{name}.scss
that says otherwise
think extension is just for webjar assets
i'll try changing that
certainly is troublesome if you get unrelated errors when you explode the jar in to the fileset
the errors look like when it's in the fileset, it isn't respecting relative file paths
since if I change it to use the full filepath within the css directory, that error goes away and it shows another
but it doesn't show any errors when using the webjar 😕
oh wait nvm... it's showing the same errors
nvm again. that was the _settings.scss file not having the right import.
hmm using the bootstrap example seems to work...
guess I know why bootstrap works and foundation doesn't - boostrap has all its scss files in one folder, while foundation uses a file heirarchy
and relative file paths apparently don't work with boot-sass
ah, good to know
but probably it is an easy patch to boot-sass
well there's been an issue open on it since 2014 i think