This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-05
Channels
- # announcements (7)
- # babashka (61)
- # beginners (146)
- # cider (4)
- # clj-kondo (25)
- # cljsrn (29)
- # clojars (30)
- # clojure (30)
- # clojure-australia (17)
- # clojure-europe (43)
- # clojure-italy (16)
- # clojure-nl (2)
- # clojure-spec (13)
- # clojure-sweden (7)
- # clojure-uk (8)
- # clojurescript (38)
- # cursive (12)
- # datomic (42)
- # defnpodcast (2)
- # dirac (1)
- # events (5)
- # fulcro (5)
- # graalvm (43)
- # graphql (11)
- # helix (6)
- # jackdaw (13)
- # jobs (4)
- # lambdaisland (8)
- # malli (12)
- # off-topic (83)
- # pathom (9)
- # podcasts-discuss (2)
- # re-frame (6)
- # reagent (3)
- # reitit (8)
- # remote-jobs (1)
- # shadow-cljs (40)
- # vim (21)
https://reactjs.org/docs/web-components.html#using-web-components-in-react > One common confusion is that Web Components use “class” instead of “className”. Does helix handle this, or do I have to do some funk? Not actually using web components, just curious.
From the Helix docs, I found that if I passed the :class
prop into my components, it would automagically translate them to :className
In practice, it was working until I integrated with a library that clones an element or does some more complex interaction. Then, :class was not properly replaced to :className until a second render, and I just decided to use :className
as I’m anyways used to that on React (js) and don’t mind.