This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-20
Channels
- # beginners (27)
- # calva (32)
- # cider (9)
- # clojure (111)
- # clojure-spec (71)
- # clojure-uk (7)
- # clojurescript (22)
- # cursive (20)
- # devcards (1)
- # emacs (4)
- # fulcro (3)
- # hyperfiddle (3)
- # off-topic (8)
- # pathom (26)
- # planck (19)
- # quil (4)
- # re-frame (1)
- # reitit (43)
- # rewrite-clj (9)
- # shadow-cljs (13)
- # spacemacs (7)
- # uncomplicate (5)
btw, i noticed the use of ^:no-doc in some locations (e.g. custom_zipper/core.clj*). i had assumed that meant there was no documentation, but there are some instances where there is also a docstring. i haven't had much luck turning up what that means. does anyone here know or have better ideas about it?
^:no-doc indicates to codox, and now more importantly to us cljdoc, that the item should not be included in documentation it generates. I believe that the original author of rewrite-clj only wanted to generate docs for what he considered the public api.
if you have a peek at rewrite-clj’s current codox generated docs, I think you’ll get the idea: http://xsc.github.io/rewrite-clj/rewrite-clj.node.html. My intent is to match rewrite-clj here, but I will be using cljdoc.