This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (34)
- # boot (45)
- # cider (16)
- # cljs-dev (20)
- # cljsjs (1)
- # cljsrn (8)
- # clojure (207)
- # clojure-berlin (3)
- # clojure-dev (18)
- # clojure-greece (1)
- # clojure-ireland (1)
- # clojure-italy (9)
- # clojure-russia (20)
- # clojure-spec (27)
- # clojure-uk (19)
- # clojurescript (110)
- # code-reviews (2)
- # cursive (7)
- # data-science (2)
- # datomic (7)
- # devcards (1)
- # emacs (4)
- # graphql (1)
- # hoplon (2)
- # immutant (15)
- # jobs (5)
- # jobs-rus (1)
- # juxt (1)
- # luminus (7)
- # lumo (26)
- # microservices (3)
- # off-topic (27)
- # om (13)
- # onyx (11)
- # pedestal (7)
- # proton (4)
- # re-frame (24)
- # remote-jobs (1)
- # spacemacs (2)
- # specter (2)
- # unrepl (31)
- # untangled (7)
- # vim (14)
can someone help me with a task with an optional argument? For example if I have something like this:
(deftask foo  (case val "bar" (bar) "baz" (baz) (foo)))
@ag you can put the arg in there anyways and if not passed it will be
nil inside the task definition
I’m running a ring app under boot, and want to access the
/resources dir for uploads.. when I use
(io/resource "") it gives me back a cache directory used by boot.. (like
#object[java.net.URL 0x7c46a8b7 "file:/Users/adm/.boot/cache/tmp/Users/adm/src/cmsproj/3ay/-7bl902/"] )
I’m wondering if I can “reset” the resource directory path somehow, or should I use another fn to get the upload directory?
(.getCanonicalPath ( is a better way to reference actual files/folders within a project?
Hi! How I can run node.js cljs repl with boot? boot-cljs-repl work only with browsers. I need nrepl support too.
Is anybody have boot task snippet for:
(require 'cljs.repl.node 'cemerick.piggieback) (cemerick.piggieback/cljs-repl (cljs.repl.node/repl-env))
.cljs_node_replfolder. But with boot it must use tmp-dir.
Any ideas why https://github.com/cljsjs/packages/blob/master/ag-grid/build.boot#L61-L63 would give me this error on Windows:
does anyone recall the technical reason we can’t set the :jvm-opts in boot the same way we do in project.clj in lein ?
so once the Clojure code needed to parse build.boot is ready, it's too late to change JVM settings
does boot offer some sort of copy operation? I have a weird case where I want to
sift :move something into two directories, but invoking sift move twice doesnt seem to place the item into both paths (as expected)
so before I go making a copy task, I wanted to make sure there’s not something simple I’m missing with the built-ins
My project depends on
adzerk-oss/boot-cljs-repl "0.3.3", but when running
boot show -u it lists version 0.3.2 as an available update
boot show -u shows outdated versions all the time. There's an issue: https://github.com/boot-clj/boot/issues/577
Do any boot-http users have an opinion on this PR/issue: https://github.com/pandeiro/boot-http/issues/55
Quick statement of problem: Jetty does not default to UTF-8, some JS libs are written with unicode chars, breakage ensues
Solution offered: just inject UTF-8 charset into headers on everything boot-http serves
My concern: What if the thing being developed is deployed w/o boot-http somewhere, and the default charset in the production CDN or whatever is not UTF-8?
boot-http can detect and emit a warning, plus expose an options for doing what you said above?
Thanks @richiardiandrea - guess I will merge that, document, and wait to see if anyone has issues with it
given the above SO thing, I was even thinking if this should be a require parameter, no defaults 😄 maybe too extreme
But given most web developers probably want the UTF-8 charset 99.9% of time... we might say it's a convention and try to serve that use-case
If it was me, I'd be opinionated and add UTF-8 headers by default, and add a configuration option for changing/removing them.
In Python-land, I've used the chardet library for guessing character sets of text files and it mostly works, but is very slow. I think it was something like hundreds of ms for megabyte of text on modern laptop.
(and it's not because it's poor library, it just works hard to be as correct as it can :P)
Yes @miikka good points; we'll do default + configuration option, that seems like the sweet spot IMO