This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-14
Channels
- # aleph (1)
- # announcements (1)
- # beginners (59)
- # boot (2)
- # calva (5)
- # cider (8)
- # clj-kondo (6)
- # cljdoc (5)
- # cljsrn (11)
- # clojure (123)
- # clojure-dusseldorf (1)
- # clojure-europe (4)
- # clojure-italy (22)
- # clojure-losangeles (4)
- # clojure-nl (10)
- # clojure-spec (18)
- # clojure-uk (22)
- # clojurescript (103)
- # cursive (32)
- # data-science (1)
- # datomic (21)
- # events (2)
- # figwheel (1)
- # fulcro (12)
- # graalvm (3)
- # graphql (8)
- # jobs (2)
- # kaocha (4)
- # klipse (2)
- # lein-figwheel (4)
- # leiningen (23)
- # off-topic (11)
- # planck (11)
- # re-frame (8)
- # reagent (2)
- # reitit (3)
- # rewrite-clj (1)
- # ring (1)
- # ring-swagger (31)
- # schema (2)
- # shadow-cljs (66)
- # spacemacs (3)
- # specter (16)
- # sql (9)
- # tools-deps (16)
- # vim (26)
Something’s up with the docs site? There’s an error message in the top left, and no API docs. https://cljdoc.org/d/planck/planck/2.24.0/doc/readme
Seems to be working again. Is it working for you @U06CM8C3V?
No, I’m still seeing “API import failed in build #17319” in red letters on a red bg in the top left corner.
Under “Namespaces” on the left, it says “We couldn’t find any namespaces in this artifact…” plus some additional info.
Hmmm. This might be a limitation of cljdoc not understanding how a JavaScript library can be exposed. What do you think @U04VDQDDY?
Yeah, cljdoc appears to be a bit fragile when it uses the analyzer to try to parse code. I think they were discussing using clj-kondo's parser, which may help with these sorts of issues.
The 2.23 docs are still good tho