Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Eventually, I'm sure there will be a 4th edition of Programming Clojure and it will cover those tools in greater detail, but if you find issues or questions, feel free to file them at https://github.com/clojure/clojure-site/issues or ask on https://ask.clojure.org .
One thing that really helps with debugging is learning to use tap>. Even after a decade of using Clojure, I found it game changing. I personally use it with djblue/portal, which has a lot of bells and whistles, but isn't too hard to get going with the basics. You don't need an UI for tap>, though, if you don't want it.
There is also https://github.com/jpmonettas/flow-storm-debugger/ which is a debugger I'm currently working in. Allows you to step over the code and other features. You can also work with `tap>` by using the Taps tab and it can help you find where the errors are coming from.
When I'm looking for tooling related stuff I do always check practical.li (https://practical.li/clojure/) since it probably has a good, if terse, description and mostly has links to the good documentation (or at least the best available).
Related posts
- FlowStorm a omniscient time travel debugger for Clojure/CLJS
- What I Have Changed My Mind About in Software Development
- ANN ClojureStorm: Omniscient time travel debugging for Clojure
- Debugging Lisp: trace options, break on conditions
- FlowStorm - Flow Docs, experimental execution derived documentation for Clojure