This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-16
Channels
- # beginners (1)
- # boot (69)
- # carry (1)
- # cider (29)
- # cljs-dev (17)
- # cljsrn (100)
- # clojure (13)
- # clojure-austin (13)
- # clojure-brasil (1)
- # clojure-dev (1)
- # clojure-korea (3)
- # clojure-russia (3)
- # clojure-spec (20)
- # clojure-uk (5)
- # clojurescript (45)
- # cloverage (3)
- # datomic (5)
- # figwheel (1)
- # hoplon (198)
- # klipse (25)
- # lein-figwheel (2)
- # leiningen (3)
- # off-topic (35)
- # om (7)
- # om-next (2)
- # onyx (8)
- # proton (8)
- # re-frame (3)
- # untangled (1)
- # vim (13)
> (->> (with-meta #{} {:I :am-lost}) (s/conform (s/coll-of strings?)) meta)
{:I :am-lost}
> (->> (with-meta #{} {:I :am-lost}) (s/conform (s/coll-of string?)) meta)
nil
I get the behavior, but I wanted to fdef
check the metadata after a function call in the :fn
. However, the :fn
only has the conformed return values, so I don’t have the metadata. Any ideas how to do this. Or would you just say I shouldn’t include it in metadata?
Hello everyone! I am going crazy on a cljs.spec strange behavior.
I use (s/fdef)
and (cljs.spec.test/instrument)
in my dev mode to catch non-conform arguments. For a strange reason my spec-ed functions keep beeing called as if a generator was forever running. I have cljs.spec.test
in my dependencies but I don't call it anywhere at the moment… any idea why ?
jetzajac: s/keys
?
depends on what you meant by "named arguments" I guess
@ggaillard i have the same problem using cljs.spec.test/instrument! i’m glad it’s not just me
I'm not crazy! Thank you! ^^ I can't manage to reproduce it too. I'm building a re-frame app and this situation always appear after a page refresh, when React tries to render some spec-ed Reagent components. I searched deeply into tens of stacktraces but found nothing particular 😞
fwiw this happens for me in http://github.com/jrheard/voke, which has very few dependencies
but again i can’t figure out what’s going on, mainly because the behavior is inconsistent so coming up with a repro is maddening/difficult
@jetzajac: oh if you mean kwargs then cat and a nested keys* for the options
@alexmiller: thanx! this is what i was looking for
@ggaillard btw while you’re using cljs.spec.test, be wary of http://dev.clojure.org/jira/browse/CLJS-1808 and http://dev.clojure.org/jira/browse/CLJS-1812 ; fixes for both are awaiting review by @dnolen
I struggled with the first one (ended up looking the source). Thanks a lot for the second one !