flow-storm-debugger icon indicating copy to clipboard operation
flow-storm-debugger copied to clipboard

A debugger for Clojure and ClojureScript with some unique features.

Results 41 flow-storm-debugger issues
Sort by recently updated
recently updated
newest added

When jumping around a flow sometimes we find interesting places we want to come back later. Being able to write down the trace-index and/or bookmark it seems useful.

enhancement

Currently only the pretty print panel supports displaying meta, would be useful to also have it on the value inspector.

enhancement

Need to implement `flow-storm.runtime.values/*values-references` in a way they can be cleaned up on flow close and tap clear

bug

Sometimes the results are too big to understand by scrolling thru its pprint in the result pane. Would be great to have a EQL filter (like datomic pull) to narrow...

enhancement

Not sure yet if direct calling is possible in both clj & cljs. Putting a call on the clipboard could also work. Thanks Compte Deouf for the idea!

enhancement

When uninstrumenting a defprotocol form we get : ![latest-screenshot](https://user-images.githubusercontent.com/786299/182451123-cd4c2d92-3fd3-4bb5-a38d-124792858844.png)

bug

Add a button to the callstack tree tool that allows to quickly expand and highlight the current frame the debugger is in.

enhancement

Quoting Carlo on slack : ``` I can see a way of using the trace information in a lot contexts in the development flow. On the top of my head:...

enhancement

Idea posted by @folcon on clojurians slack. Leaving it here because I think it is interesting to explore it in the future: Not sure if you want to support this,...

enhancement

It would be nice to move around the debugger by using the keyboard

enhancement