is there a way to get the error/stacktrace when I'm evaluating expressions in cider? seems like since this returns a promise I just get the promise printed, and stuff gets updated "later", at which point I don't see anything even if the app blows up

like lets say I do (defn root [] ...) instead of (defn root [{:keys [title]}] ...) and eval the buffer, it seems to just work, but I don't get any window to show up --- iirc there was another case where I could eval something and it would error out and close the window but I'd not get an error message because calling (renderer) returns a pending promise

is there a way to use a var-quoted function instead of just the function in a component definition? as in to use :fx/type #'my-component instead of :fx/type my-component, so that I wouldn't have to re-evaluate every single component definition that uses my component to get the UI to update?

is there some way to make the stacktraces more filtered/reasonable? for example when I have an invalid url for an image-view the resulting stacktrace is 500 lines, and they all look the same so it's a bunch of scrolling up in cider repl on every error 😩 I guess if I deref I get the error at the bottom too tho which is nicer, but the output is still gigantic