Clojurians Log v2

Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.505 • Fix: https://github.com/BetterThanTomorrow/calva/issues/2806 (Hopefully) • Fix: https://github.com/BetterThanTomorrow/calva/issues/2808 Thanks to everyone involved in hunting this and helping me with testing and clues! 🙏 ❤️ calva

Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.506 • https://github.com/BetterThanTomorrow/calva/issues/2802 Now the API let’s you register a listener for Calva REPL output messages. See https://calva.io/api/#replonoutputlogged

https://clojurians.slack.com/archives/C8NUSGWG6/p1746220630998139

Recently @pez @daslu and I have been imagining how Clojure tools can be used more conveniently from Calva. We wanted to add commands and keybindings for the Clay (data visualization) library. The result of that thinking is Calva Power Tools https://github.com/BetterThanTomorrow/calva-power-tools, a companion extension. Calva Power Tools is a contributor friendly way for library and tool authors to provide commands in VSCode without making a separate extension. The hope is that people will contribute commands and keybindings for their favorite Clojure tools. If you use a Clojure tool and think that it could benefit by being included in the Power Tools extension, it would be great if you could submit a PR to add it, or discuss it with us. Some ideas are Malli validation, Flowstorm debugging, Kondo linting, Hyperfiddle rendering... I'm sure there are many more! What Clojure tool actions have you found very helpful to bind to a key that we might be able to share as commands?