This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-02
Channels
- # adventofcode (47)
- # announcements (7)
- # aws (1)
- # babashka (52)
- # beginners (80)
- # boot (3)
- # calva (19)
- # cider (9)
- # cljs-dev (1)
- # clojure (48)
- # clojure-brasil (1)
- # clojure-dev (27)
- # clojure-europe (3)
- # clojure-madison (3)
- # clojure-nl (29)
- # clojure-spec (11)
- # clojure-sweden (1)
- # clojure-uk (49)
- # clojurescript (66)
- # core-async (20)
- # cryogen (4)
- # cursive (13)
- # data-science (7)
- # datomic (5)
- # emacs (30)
- # figwheel-main (11)
- # fulcro (15)
- # graphql (8)
- # jobs (5)
- # joker (17)
- # lambdaisland (1)
- # leiningen (2)
- # malli (2)
- # off-topic (5)
- # pathom (22)
- # re-frame (12)
- # reagent (29)
- # reitit (2)
- # ring (10)
- # shadow-cljs (57)
- # specter (3)
- # tools-deps (22)
- # vim (5)
- # xtdb (7)
I have that latest joker on MacOS (installed via brew)
$ cat h.joke
(ns hu.evernode.test
"Hiccup test"
(:use [joker.hiccup]))
(println (html [:span {:class "foo"} "bar"]))
$ joker --lint h.joke
h.joke:5:11: Parse error: Unable to resolve symbol: html
however it works
$ joker h.joke
<span class="foo">bar</span>
$ joker -v
v0.14.0
should I file an issue on github?
Quoting from the README.md at https://github.com/candid82/joker:
If you use :refer :all Joker won't be able to properly resolve symbols because it doesn't know what vars are declared in the required namespace (i.e. clojure.test). There are generally three options here:
Since :use
is similar to :refer :all
, the advice pertains. Check out the three options listed in that file.When using ns-sources
, why do you map a string for the namespace, rather than a symbol? Seems odd. Also, feels odd to put the ns-sources
before the ns
call, rather than inside it, ala :require, etc.
ANN: net.lewisship.multi v1.0.0
net.lewisship.multi
is a complement to joker.tools.cli that allows a single tool, a Joker script, to
contain multiple commands, each with its own command line options and arguments.
https://github.com/hlship/multi
I think the ns-sources
mechanism is promising, but I think it could be a bit easier; for instance, a special case for libraries that are available from github; maybe
(ns-sources {"net.lewisship.multi" {:github "hlship/multi" :version "v1.0.0"}})
would expand to
Woah! That ns-sources
looks awesome!
> {:github "hlship/multi" :version "v1.0.0"}
:version
here is a ref/tag?
That was just a strawman; right now only :url is supported, not :github. Maybe :tag would be more be more accurate than :version?