This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-16
Channels
- # announcements (18)
- # architecture (11)
- # babashka (20)
- # beginners (32)
- # biff (21)
- # calva (70)
- # clerk (6)
- # clj-kondo (16)
- # clj-otel (5)
- # cljsrn (8)
- # clojure (94)
- # clojure-austin (1)
- # clojure-australia (1)
- # clojure-europe (68)
- # clojure-nl (2)
- # clojure-norway (6)
- # clojure-uk (2)
- # clojurescript (13)
- # conjure (1)
- # core-logic (1)
- # cursive (7)
- # data-science (2)
- # datahike (3)
- # datomic (12)
- # emacs (33)
- # etaoin (1)
- # fulcro (8)
- # graalvm (2)
- # graphql (1)
- # honeysql (1)
- # hyperfiddle (97)
- # improve-getting-started (40)
- # jobs (2)
- # jobs-discuss (12)
- # lsp (9)
- # membrane (6)
- # nbb (2)
- # off-topic (16)
- # portal (6)
- # re-frame (2)
- # reagent (3)
- # releases (2)
- # remote-jobs (1)
- # tools-deps (7)
- # xtdb (38)
Released FlowStorm 3.3.320 FlowStorm is a Clojure and ClojureScript tool suite which contains a debugger and types docs generation tooling This release doesn't add any new features but fixes a bunch of issues reported by users. Since last announced release : • Upgrades to openjfx 19.0.2.1 which solves the tool failing to start on hombrew openjdk under macos ventura • Improves deep function instrumentation (with one click you can instrument a fn and recursively any called fn) • Fix type hinted fn instrumentation on clojure 1.10 • Support instrumenting functions forms like (let [...] (defn foo [] ...)) • Fix code instrumentation where libraries like potemkin/import-vars are used • Improve docs file generation • Fix namespace instrumentation for files that end with a comment • Fix OS theme detection exceptions • And more Thanks to everybody who reported issues, and a big thanks to Roam Research and people sponsoring the project. Repo : https://github.com/jpmonettas/flow-storm-debugger User guide : https://jpmonettas.github.io/flow-storm-debugger/user_guide.html Cheers!
Initial release of https://github.com/NoahTheDuke/spat - Next-Generation kibit-style linter Reads clojure/script code, checks for known "bad forms", and prints the more idiomatic form:
[:not-nil?] src/noahtheduke/spat.clj - 756:14
(not (nil? ?x))
Consider using:
(some? ?x)
Decided to release this in the barest bones version to see how folks like it. It can be run as a command-line tool with @borkdude’s bbin, or turned into an uberjar and run manually. I hope to get it even faster (maybe with GraalVM?), but this is a good place to start.@UEENNMX0T If you can emit output like clj-kondo's text output, I think it's pretty easy to hook this up to emacs
E.g. copy and modify this plugin a bit: https://github.com/borkdude/flycheck-clj-kondo
Excellent, I don’t use emacs but I do gather all of the data and can output it.
what editor are you using? intellij? I've had similar stuff with clj-kondo + intellij based on the same output
I use neovim and rely singularly on clojure-lsp’s errors. But i can set this up
ok, if you spit out clj-kondo's format, then neovim can also pick this up using ale or some other stuff, check out the same editor-integration.md link, but for vim
Excellent
Btw how much did it help in speed to use s-expressions rather than rewrite-clj nodes?
You can also integrate into neovim with null-ls.nvim. I use this and it works well. Here is an example parsing a cli program https://github.com/jose-elias-alvarez/null-ls.nvim#parsing-cli-program-output