This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-23
Channels
- # beginners (27)
- # boot (8)
- # cider (17)
- # cljs-dev (8)
- # cljsrn (5)
- # clojure (56)
- # clojure-dev (34)
- # clojure-gamedev (4)
- # clojure-italy (32)
- # clojure-nl (22)
- # clojure-poland (3)
- # clojure-russia (17)
- # clojure-spec (31)
- # clojure-uk (48)
- # clojurescript (47)
- # core-async (41)
- # cursive (13)
- # datomic (22)
- # emacs (9)
- # figwheel (7)
- # fulcro (18)
- # graphql (3)
- # hoplon (15)
- # jobs-discuss (38)
- # keechma (1)
- # luminus (10)
- # off-topic (42)
- # onyx (8)
- # overtone (3)
- # protorepl (5)
- # re-frame (42)
- # reagent (6)
- # reitit (3)
- # schema (4)
- # shadow-cljs (39)
- # slack-help (5)
- # spacemacs (8)
- # specter (1)
- # tools-deps (36)
- # uncomplicate (9)
- # vim (34)
I have a problem with a recursive spec in a cljc file. it’s the ::tree (and ::node) spec here https://github.com/stevebuik/Stu/blob/master/src/cljc/viz/core.cljc
works fine within this project but when invoked via an installed dep in another project, this spec fails to load
I have never noticed this, but basically the output of clojure spec does not expand nested specs:
user=> (doc my-ns.core/test-fn)
-------------------------
my-ns.core/test-fn
([n])
Spec
args: (cat :n :test-ns)
ret: any?
nil
Is there a way to see what the :test-ns
spec actually is?you can invoke doc
on spec names too
I would expect that to be a qualified keyword above though
not sure if you altered the output
user=> (doc :clojure.core.specs.alpha/args+body)
-------------------------
:clojure.core.specs.alpha/args+body
Spec
(cat :args :clojure.core.specs.alpha/arg-list :body (alt :prepost+body (cat :prepost map? :body (+ any?)) :body (* any?)))
for example
do I need to namespace it? I have a global :test-ns
only
spec names are expected to be namespaced
maybe we’re talking about different things
oh right
spec names should be qualified, as in :foo/bar
no you are right my bad
perfect thanks it works fine 😉