This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-10
Channels
- # announcements (9)
- # aws (11)
- # babashka (37)
- # beginners (97)
- # biff (2)
- # calva (73)
- # clj-kondo (17)
- # cljfx (3)
- # clojure (89)
- # clojure-europe (45)
- # clojure-norway (12)
- # clojurescript (17)
- # datahike (8)
- # datomic (13)
- # deps-new (4)
- # figwheel-main (1)
- # graalvm (2)
- # hyperfiddle (8)
- # introduce-yourself (6)
- # leiningen (38)
- # lsp (57)
- # malli (13)
- # nbb (46)
- # off-topic (40)
- # pathom (3)
- # polylith (8)
- # rum (4)
- # shadow-cljs (14)
- # spacemacs (1)
- # sql (11)
- # xtdb (10)
Just released https://github.com/polyfy/polylith/releases/tag/v0.2.15-alpha: • https://github.com/imrekoszo/polylith-kaocha test runner - https://github.com/polyfy/polylith/pull/196 • XDG support - https://github.com/polyfy/polylith/pull/228 • Support for multiple source directories - https://github.com/polyfy/polylith/issues/206 • And more…
So many improvements. Great work! I like poly is using XDG directories - a ton of improvements. Will update to it out now and give feedback.
Great!
FlowStorm Clojure and ClojureScript debugger 2.3.131 is out FlowStorm is a Clojure and ClojureScript debugger with some unique features. 2.3.131 includes new features : - New lazy and recursive value inspector (https://jpmonettas.github.io/flow-storm-debugger/user_guide.html#_value_inspector) - New tap tool to work with tap> (https://jpmonettas.github.io/flow-storm-debugger/user_guide.html#_taps_tool) - Support for light and dark themes, in selected or automatic mode. Checkout the user guide for more info. (thanks to Liverm0r!) - Thread tabs can be closed and reordered - New functions for shutting down the debugger gracefully (for using in state components) and a bunch of bug fixes. Github repo : https://github.com/jpmonettas/flow-storm-debugger/ User Guide https://jpmonettas.github.io/flow-storm-debugger/user_guide.html Show up in #flow-storm if you are interested in this kind of stuff. Cheers!
Interesting! It would help me (and likely other would-be users) to have an intro paragraph in the github explaining the what/why of the project i.e. I see that it's a debugger, why should I pick yours? (nowadays I don't use a debugger at all tbh, open to going back to them)
hi @U45T93RA6, sure, good idea. I gave a talk reacently that goes over exactly that question, the slide is here: https://youtu.be/A3AzlqNwUXc?t=102
@U45T93RA6 someone else was asking the same on redit, so there is also my answer there https://www.reddit.com/r/Clojure/comments/wkw8qr/comment/ijqq8a4/?utm_source=share&utm_medium=web2x&context=3