This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-28
Channels
- # announcements (1)
- # beginners (183)
- # boot (2)
- # clara (4)
- # cljs-dev (20)
- # clojure (59)
- # clojure-dev (7)
- # clojure-nl (1)
- # clojure-serbia (1)
- # clojure-sg (1)
- # clojure-spec (4)
- # clojure-uk (15)
- # clojurescript (77)
- # clr (1)
- # data-science (9)
- # datomic (23)
- # docs (3)
- # duct (15)
- # emacs (8)
- # events (1)
- # fulcro (6)
- # instaparse (3)
- # juxt (1)
- # lumo (9)
- # off-topic (18)
- # perun (2)
- # portkey (13)
- # reagent (2)
- # reitit (11)
- # ring (10)
- # shadow-cljs (158)
- # tools-deps (34)
I have this idea of reusing fulcro components between web and react native: in many cases the web component and its RN equivalent only differ in render method
I wonder if I can do something like:
(defsc MyComponent {:ident ... :query..}) ;; no render
(def MyComponentWeb (extend-component MyComponent {:life-cycle-methods ...})
(def MyComponentRN (extend-component MyComponent {:life-cycle-methods ...})
what do you think?
@myguidingstar I think they are different UI's, IMO fulcro makes that easy that justify duplication, after all most of the complexity is on the server, just declare the components as you need, I don't see much value on trying to share, might end up hurting
👍 4
in my experience trying to create this extension classes tend to do bad with time
better to have the queries and idents as variables somewhere else and just re-use it