This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-10
Channels
- # aws (39)
- # babashka (4)
- # beginners (5)
- # biff (25)
- # cider (14)
- # clj-on-windows (40)
- # clojure-europe (36)
- # clojure-gamedev (1)
- # clojure-losangeles (4)
- # clojure-norway (51)
- # clojure-spec (5)
- # clojure-uk (2)
- # clojurescript (2)
- # clr (176)
- # data-science (10)
- # datalevin (17)
- # datomic (7)
- # deps-new (4)
- # docs (3)
- # emacs (12)
- # figwheel (3)
- # figwheel-main (5)
- # hyperfiddle (20)
- # instaparse (3)
- # introduce-yourself (8)
- # lsp (66)
- # malli (43)
- # off-topic (4)
- # rdf (11)
- # reagent (5)
- # releases (2)
- # sci (11)
- # shadow-cljs (24)
- # slack-help (2)
- # specter (7)
- # tools-deps (3)
- # xtdb (48)
I have a JS react component I instanciate like so: [:> TabView]. If I make a component that outputs its relevant [:> TabPanel] .. I get no output. If I put the [:> TabPanel] directly as a child of the TabView, works great. Any clues?
Maybe TabView
really wants for instances of TabPanel
to be its direct children.
Or maybe there's a mistake in how you're creating the wrapper component.
I think its the former, I tried a really static payload for the TabPanel
and it behaved similarly identically. Is there any way to write a fn to output the direct TabPanel
? I know I’ve had to use reagent.core/as-element
to pass components in fn parameters with this library, but it didn’t seem to do the trick here.