Not yet, but here are some examples https://github.com/djblue/portal/blob/master/src/examples/data.cljc#L112-L191

I think portal has some higher level viewers that will map data to vega/vega-lite, but if you want custom stuff, you can use the vega/vega-lite viewer directly 👍

So I have this working nicely, locally. With :portal.nrepl/eval true in the metadata.

What are the red yellow orange dots meant to be at the top of the stdio stuff?

Just decoration that I plan on making the expand / collapse buttons in the future. It's suppose to look like a terminal 😆

Ah, a Mac terminal.

Yeah, the viewer will also correctly handle color escape codes 👌

https://djblue.github.io/portal/?content-url=https://gist.githubusercontent.com/djblue/9a2cd250e061f62ce527b20648fd8256/raw/e7bd673df60b3c503306956b950bb9589ba480eb/data.clj&content-type=application/edn is what portal's build output looks like. It's using the same prepl viewer

It supports three tags: :out, :err and :tap

Wow, nice!

OK, took me a bit of messing about to get the results I wanted in the right order but...

That's the result of my "run tests" hot key which invokes parts of clojure.test and then tap>'s the result (summary hash map). So now it is show the report card, then the standard output, then the actual value I tapped. That means that the most recent tapped value is still the most recent item in Portal, even if there is output or test results, and I can still use my various hotkeys to drive Portal's UI to expand parts of it or cycle through viewers, as before.

What was the go to file/line hot key in Portal where you're on logging style line?

goto-definition should be mapped to g + d

Ah, yes, and it loads it in the portal window group. Thanks.

So here's where I've ended up and this works very nicely:

(ns dev)

(defonce *v (atom nil))
(defonce was-tap (atom false))

(defn submit
  [v]
  (let [m (try (meta v) (catch Exception _))]
    (if (:portal.nrepl/eval m)
      (let [{:keys [stdio report level]} v]
        (when report
          ((requiring-resolve 'portal.api/submit) report))
        (when stdio
          ((requiring-resolve 'portal.api/submit) stdio))
        (when (= level :error)
          ((requiring-resolve 'portal.api/submit) v))
        (when @was-tap
          (reset! was-tap false)
          ((requiring-resolve 'portal.api/submit) @dev/*v)))
      (do
        (when @was-tap
          (reset! was-tap false)
          ((requiring-resolve 'portal.api/submit) @dev/*v))
        (reset! dev/*v v)
        (reset! was-tap true)))))

(with-meta {:portal.nrepl/eval true
                        :portal.viewer/for
                        {:code :portal.viewer/code
                         :time :portal.viewer/relative-time}
                        :portal.viewer/code {:language :clojure}})
            tap>)))

Nice! I think meta is safe without try catch :thinking_face:

Yup, thanks. Will simplify.

Yeah, this is working really well for me... I get better feedback on "normal" evaluations via Calva and I still have my previous tap> workflow with hotkeys to drive navigation in Portal.

The prepl and test report viewers could use some ux polish so if you think of anything, let me know. I still need to add filter failing for the test viewer

I'm the wrong person to ask about UI/UX 🙂 but if I run into anything and have suggestions, I'll let you know.