4 ms·
And the debugging support. Good. Debugging. Support!
by KirinDave 11y ago
And the debugging support. Good. Debugging. Support!
- swannodette 11y agoThis really cannot be repeated enough times.
- KirinDave 11y agoAfter 2 years without it you go back in and it's so seductive you almost want to stop writing unit tests. Ignore this feeling even as you bask in it! :D
- 1wheel 11y agoAny tips on using it? Breakpoints in the chrome dev tools and `debugger` are a huge part of my JS workflow, but I've been having trouble wrapping my head around the InteliJ UI. I basically just want to be able to pause the program, see/move up the call stack, and use the REPL with local variables.
- swannodette 11y agoYou just click in the gutter to create a breakpoint and start a debug REPL - look at the IntelliJ Run menu.
- _halgari 11y agolet's not forget crazy stuff like going into debug mode and then evaling random clojure code in the context of the debugger
- lemming 11y agoBest of all is "stop when this exception is thrown". I use that to start 90% of my investigations.
- marxama 11y agoThis post is enough for me to decide to get this NOW.
- lemming 11y agoIf you're interested in the debugger, I spoke about it at Clojure/West this year: https://www.youtube.com/watch?v=ql77RwhcCK0 https://www.youtube.com/watch?v=ql77RwhcCK0. It shows how the debugger works and I talk about the problems debugging Clojure code, of which there are many.