Thanks for adding this

Is there a way to configure the default inspector viewer to expand?

At what level of depth?

I currently have this:

and would like to have the mulog/data expanded

I can expand it, but when a new row is added, the expansion is reset

I had some success with setting the viewer to pprint:

There isn't an easy way to force something to be expanded currently, so using another viewer as the default would be easier

cool, that works for me right now

The tree viewer might be another option

this is fantastic

I have a hot key bound to a variant of tap> that adds metadata to ask for the tree viewer.

https://github.com/seancorfield/vscode-clover-setup/blob/develop/config.cljs#L10

Also, if these aren't being submitted via the REPL, doing something like:

(update log :mulog/data vary-meta assoc :portal.viewer/default :portal.viewer/tree)

Is there a video somewhere of this workflow? It would help me understand the effort and ROI

@U0510KXTU a video of what part exactly?

Setup to see how/effort required to setup. Then the improvement from seeing logs and test reports in portal vs ide console

It depends on what you use for logging, but here is a guide for https://github.com/djblue/portal/tree/master/examples/timbre. It's particularly nice for the logs in my app since they have a ton of context which does not print well at a terminal 👌

I patch tools.logging when I start my REPL to send data to Portal -- works really well for me: https://github.com/seancorfield/dot-clojure/blob/develop/dev.clj#L83

loving this timbre workflow. thank you! next step: getting test outputs into portal as well

re the suggestion of a video: even though the instructions are simple and easy, a short video would showing how nice it is would have hooked me earlier. just a thought @U1G869VNV