This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-16
Channels
- # announcements (2)
- # babashka (51)
- # beginners (165)
- # biff (39)
- # clara (1)
- # clj-kondo (20)
- # cljsrn (6)
- # clojure (64)
- # clojure-belgium (11)
- # clojure-conj (2)
- # clojure-europe (12)
- # clojure-nl (3)
- # clojure-norway (7)
- # clojure-uk (6)
- # clojurescript (11)
- # conf-proposals (1)
- # conjure (1)
- # core-async (19)
- # cursive (6)
- # data-science (16)
- # datomic (6)
- # deps-new (4)
- # fulcro (60)
- # funcool (3)
- # graalvm (9)
- # helix (14)
- # introduce-yourself (4)
- # jobs-discuss (13)
- # joyride (1)
- # kaocha (2)
- # malli (12)
- # off-topic (25)
- # polylith (9)
- # portal (3)
- # practicalli (1)
- # rdf (43)
- # re-frame (7)
- # reagent (5)
- # releases (5)
- # remote-jobs (8)
- # sci (5)
- # shadow-cljs (42)
- # squint (6)
- # xtdb (5)
Apologies in advance if this is a daft question, but I am trying to render a simple vega-lite chart in a REPL context, i.e., I don’t need to output it anywhere, just eyeball it. I note that there is a vega-lite viewer in portal, but I can’t find any instruction on how to use it. I have found that, if I tap a vega-lite JSON spec as a string, the portal vega-lite viewer is available, but if I convert this to EDN, it is not available, no matter whether the EDN has been read in via edn/read-string, or slimply slurped into a string. To render the Clojure form of the spec I have downloaded Oz, but I’m still curious about whether I should have been able to do this with portal. Any thoughts?
The vega-lite spec looks like:
(s/def ::name string?)
(s/def ::description string?)
(s/def ::$schema
(s/and string? #(re-matches #"\.github\.io/schema/vega-lite/v\d\.json" %)))
(s/def ::vega-lite
(s/keys :req-un [::data]
:opt-un [::name ::description ::$schema]))
This might be the missing piece :thinking_face:Many thanks for the insight! I will check what I am tapping against that spec.