This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-27
Channels
- # announcements (2)
- # asami (25)
- # babashka (124)
- # beginners (46)
- # calva (55)
- # cljdoc (70)
- # clojure (68)
- # clojure-australia (2)
- # clojure-dev (63)
- # clojure-europe (38)
- # clojure-nl (1)
- # clojure-spec (1)
- # clojure-uk (8)
- # clojurescript (56)
- # community-development (4)
- # conjure (1)
- # copenhagen-clojurians (1)
- # core-async (1)
- # cursive (3)
- # datahike (5)
- # datomic (183)
- # depstar (2)
- # figwheel-main (10)
- # fulcro (20)
- # honeysql (2)
- # hyperfiddle (1)
- # integrant (68)
- # jobs (6)
- # jobs-discuss (5)
- # juxt (1)
- # malli (13)
- # off-topic (8)
- # pathom (2)
- # rdf (10)
- # reagent (11)
- # remote-jobs (1)
- # rum (1)
- # shadow-cljs (69)
- # spacemacs (1)
- # sql (5)
- # tools-build (51)
- # tools-deps (6)
- # xtdb (24)
There’s a few unreviewed PRs currently open. I’ll try to give them a review this week but if anyone else feels like helping out by reviewing some code, please check ’em out 🙂 https://github.com/cljdoc/cljdoc/pulls
I'm a bit distracted right now, but @deleted-user if you enjoy such activities and have time/interest, please do feel free to dive in!
Yeah, I think docs should be updated, probably here: https://github.com/cljdoc/cljdoc/blob/master/doc/userguide/for-library-authors.adoc
There's also a validator of sorts... but having it check url could be a separate piece of work. https://github.com/cljdoc/cljdoc/blob/master/script/verify-cljdoc-edn And we were thinking of making a new babashka version of this thing anyway... so probably best to think about it separately.
The spec, if I remember correctly, might not be applied at analysis time... vague recentish memories... but something might be a bit non-obvious about when that user config cljdoc.edn spec is applied.
Yeah... I think I was noticing that and that's why I was working on some validation for cljdoc.edn.
I was actually playing with malli for validating cljdoc.edn (outside of thinking about a bb script) but then switched to rewrite-clj because it seemed more straightforward to get good errors with line/col.
Hmm... clj-kondo already validates bb.edn
and deps.edn
I wonder if it could validate cljdoc.edn
? I don't think its hooks support edn files.
(are we just trolling borkdude with keywords to see how many times we can get his attention?)
Gotcha. Maybe. Was thinking a custom hook hosted by cljdoc would make sense. Or would a hook for this in clj-kondo itself be of interest?
Would be nice to just have it in clj-kondo too though because that would mean you get automagic validation when you use clj-kondo
(vs. something that is external and people have to add manually)
for now I'd rather support the hook rather than having it built-in. you can get the hook via a dependency
Yeah @martinklepsch, clj-kondo supports hook export/import. Clj-kondo user will still have to opt in, but we can add instructions.
I suppose tooling that sits atop clj-kondo like clojure-lsp could choose to auto-opt-in... or make opt-in obvious/easy.
First stab at issue: https://github.com/clj-kondo/clj-kondo/issues/1392
@lee yes. seems good. the code for linting bb.edn/deps.edn is at the bottom in impl/analyzer.clj
if you want to you whip up some prototype. I can imagine a :hooks {:file {...}}
kind of thing where you have some filter on the filename or path and the hook receive the entire rewrite-edn node of the file + some other properties as a map
and possibly transform the node as well by returning it, or just leave it by not returning it or returning the same one
Yeah sounds good. What about the hook checking if files referenced in edn exist? Would that be possible or would that be a security concern?
perhaps people can add ;; cljdoc yes for realz
in their file to enable the linting
But really, I'm supposed to be working on my GraalVM failure on Windows for rewrite-clj. I swear, I used to be a focused person!