This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-20
Channels
- # aws-lambda (8)
- # beginners (37)
- # cider (43)
- # cljs-dev (12)
- # clojure (121)
- # clojure-italy (19)
- # clojure-nl (1)
- # clojure-poland (1)
- # clojure-russia (14)
- # clojure-spec (6)
- # clojure-uk (98)
- # clojurescript (28)
- # core-async (1)
- # cursive (7)
- # datomic (4)
- # emacs (63)
- # events (8)
- # fulcro (19)
- # graphql (4)
- # hoplon (3)
- # mount (1)
- # nrepl (101)
- # off-topic (15)
- # om (3)
- # pedestal (2)
- # portkey (31)
- # protorepl (2)
- # re-frame (26)
- # reagent (26)
- # reitit (2)
- # shadow-cljs (58)
- # spacemacs (8)
- # specter (5)
- # sql (56)
- # test-check (11)
- # tools-deps (48)
- # vim (52)
I wrote a small library that addresses the above problem -- instrumenting initial/global function calls. It takes a slightly different approach than fdef. During development it immediately wraps function calls with assertions on a function's args and ret value. Thoughts on this idea? 🙂 https://github.com/Provisdom/defn-spec
Ah you're right. I did not realize orchestra did more than enable :ret checking for instrumentation. This approach is still different than orchestra's defn-spec. Orchestra's defn-spec also doesn't have great IDE support.
@U3UFFB420 Added an excerpt in the README addressing this: https://github.com/Provisdom/defn-spec#how-is-this-different-from-orchestra.
@U083D6HK9! I pretty much skimmed the README at work. Now I gave it a read and see more clearly the purpose of the lib (BTW, that's a well written README). My thoughts are: I liked it. You just don't care anymore about instrument.