This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-06
Channels
- # aws-lambda (8)
- # beginners (49)
- # boot (13)
- # braveandtrue (2)
- # cider (12)
- # cljs-dev (15)
- # cljsrn (2)
- # clojure (143)
- # clojure-italy (8)
- # clojure-nl (17)
- # clojure-spec (22)
- # clojure-uk (21)
- # clojurescript (145)
- # code-reviews (1)
- # cursive (33)
- # data-science (14)
- # datomic (25)
- # emacs (3)
- # events (1)
- # fulcro (48)
- # graphql (1)
- # onyx (15)
- # perun (5)
- # play-clj (2)
- # protorepl (1)
- # re-frame (27)
- # remote-jobs (3)
- # ring (3)
- # rum (7)
- # shadow-cljs (87)
- # specter (4)
- # test-check (14)
- # testing (2)
- # tools-deps (9)
I tracked it down to this commit: https://github.com/boot-clj/boot/commit/197f991324d9207f5d4b7b1828dd54ff61aadd09
[edn]
or [sym]
used to be treated as accumulated arguments (that you can specify multiple times), now that only works for sets. Not sure if that's the desired behavior, but in any case, there are still plenty of tasks that have such arguments.
Also, even if that's intended, this is a breaking change for anyone with custom tasks that relied on this syntax.
Uhm yes this seems different now - we could revert but it will break the pom with parent feature, I will have a look later today
Probably a buggy implementation ...no tests were around that oops
Thanks definitely
Perhaps, some other notation is needed for this SYM:VER=PATH
thing. Something more explicit.
Can there be nested lists in a parameter list? Because I could flatten in case we have one only