This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-13
Channels
- # aws (5)
- # bangalore-clj (2)
- # beginners (74)
- # boot (2)
- # cider (12)
- # cljs-dev (5)
- # cljsjs (2)
- # cljsrn (7)
- # clojure (41)
- # clojure-boston (4)
- # clojure-brasil (3)
- # clojure-russia (12)
- # clojurescript (73)
- # cloverage (35)
- # datomic (7)
- # euroclojure (1)
- # hoplon (34)
- # immutant (1)
- # luminus (9)
- # onyx (7)
- # overtone (3)
- # parinfer (1)
- # proton (2)
- # re-frame (3)
- # reagent (5)
- # spacemacs (5)
- # testing (2)
- # untangled (3)
- # yada (3)
I mean, Iโll let you get away with it if youโd like to call it quits โ itโll be a lot easier to test that code if we get to have dependencies โ at least the code around it will have more facilities for testing
most of the stuff is wrapped in a with-out-writer macro that you can't with-redef-fn in a test
then you need forms to test with and i thought i'd use the content of the sample.clj
then you need to read that back in as testdata and the functions in source.clj almost do what you want, but not quite
and after all that i discovered that the gather-stats form reads all the source files again during reporting
which is probably not what we want in the long run either, because it effectively prohibits output plugins
the reason we reread the source files is i believe because it was the simplest way to get the formatting right
if the whole gather-stats would be in it's own package or such, reports would be "out" only