This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-03
Channels
- # beginners (167)
- # boot (22)
- # chestnut (3)
- # cider (9)
- # clojure (107)
- # clojure-berlin (1)
- # clojure-greece (3)
- # clojure-italy (6)
- # clojure-losangeles (6)
- # clojure-russia (8)
- # clojure-spec (71)
- # clojure-uk (42)
- # clojurescript (186)
- # community-development (1)
- # core-async (12)
- # core-typed (1)
- # css (15)
- # cursive (29)
- # data-science (11)
- # datomic (8)
- # defnpodcast (28)
- # duct (2)
- # fulcro (169)
- # graphql (6)
- # hoplon (3)
- # jobs-discuss (1)
- # kekkonen (5)
- # leiningen (11)
- # lumo (7)
- # off-topic (14)
- # om (1)
- # other-languages (14)
- # portkey (7)
- # re-frame (27)
- # reagent (14)
- # remote-jobs (1)
- # ring-swagger (5)
- # rum (15)
- # shadow-cljs (52)
- # spacemacs (59)
- # specter (78)
- # test-check (3)
- # vim (9)
- # yada (23)
there’s a function called reactify-component
in reagent.core
that says it does just that
remember that a React (functional) component is just a function that returns a React element
so you could also easily export a clojurescript function that returns (r/as-element [:div "or any other Reagent hiccup"])
cljs functions are just js functions, so you can use it from your JS React code
@kishanov http://reagent-project.github.io/news/news050.html has some info on that
hi! there is something strange going on in one of the libraries I use. Is there some way of debugging what's going on in that particular function? I've tried to use the debugger of cider, but it did not stop, so I guess the function was not properly reloaded..
@pwrflx dirac
may be a help? Althought some effort required to set it up.