This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-13
Channels
- # babashka (7)
- # babashka-sci-dev (3)
- # beginners (29)
- # biff (16)
- # calva (2)
- # clojars (1)
- # clojure (50)
- # clojure-austin (5)
- # clojure-europe (29)
- # clojure-france (8)
- # clojure-nl (3)
- # clojure-uk (3)
- # clojured (10)
- # clojurescript (19)
- # code-reviews (3)
- # core-async (22)
- # cursive (5)
- # data-science (11)
- # datalevin (1)
- # datomic (10)
- # eastwood (4)
- # helix (4)
- # introduce-yourself (2)
- # jobs (1)
- # jobs-discuss (1)
- # joyride (6)
- # leiningen (4)
- # london-clojurians (2)
- # lsp (82)
- # malli (7)
- # meander (12)
- # minecraft (3)
- # nbb (14)
- # off-topic (52)
- # podcasts (3)
- # portal (3)
- # re-frame (32)
- # reagent (9)
- # releases (2)
- # shadow-cljs (95)
- # tools-deps (14)
for error boundaries, you can use helix.core/defcomponent but it’s not super well documented
I'll try that, if it makes better error catching.
here's a "simple" example:
(defcomponent error-boundary
(constructor
[this]
(set! (.-state this) #js {:error nil}))
^:static
(getDerivedStateFromError
[this error]
#js {:error error})
(render
[this props state]
(if-let [error (.-error ^js state)]
(if (:on-error-component props)
($ (:on-error-component props))
(d/div (pr-str error)))
(:children props))))
👍 1