This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-28
Channels
- # aleph (3)
- # beginners (10)
- # boot (135)
- # clara (2)
- # cljsjs (2)
- # cljsrn (1)
- # clojure (68)
- # clojure-austin (4)
- # clojure-france (2)
- # clojure-japan (1)
- # clojure-spec (30)
- # clojure-uk (11)
- # clojurescript (48)
- # component (65)
- # cursive (5)
- # datomic (40)
- # dirac (5)
- # emacs (3)
- # events (16)
- # funcool (2)
- # klipse (46)
- # lein-figwheel (2)
- # luminus (8)
- # off-topic (4)
- # om (7)
- # other-languages (4)
- # parinfer (21)
- # re-frame (15)
- # reagent (30)
- # ring (1)
- # ring-swagger (9)
- # rum (3)
- # specter (7)
- # test-check (8)
- # testing (5)
- # vim (21)
- # yada (4)
@viebel so great!
@lucasbradstreet which one? the blog post or the interactive doc?
Both are great. I love the docs versions with inline testable examples though. I want it everywhere 😄
In the example where the property is incorrect i.e. (let [s (sort v)] (< (first s) (last s))))) it might be useful to say that both properties and the code they test can be incorrect. Usually you’re trying to start from a correct property and find a bug in your code, but sometimes your code ends up testing your properties instead. I’m not sure how obvious it’ll be to a new user
good input
how would you fix it @lucasbradstreet ?
@lucasbradstreet you can live interactive doc with the codox klipse theme. It’s super easy to integrate in any lib that is cljs ported