This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-03
Channels
- # beginners (112)
- # boot (13)
- # cider (17)
- # cljsjs (2)
- # cljsrn (8)
- # clojure (57)
- # clojure-spec (2)
- # clojure-uk (5)
- # clojurescript (51)
- # cursive (4)
- # data-science (15)
- # datomic (1)
- # duct (17)
- # garden (4)
- # lein-figwheel (49)
- # midje (1)
- # nyc (1)
- # off-topic (8)
- # pedestal (1)
- # portkey (20)
- # re-frame (4)
- # reagent (27)
- # ring (1)
- # shadow-cljs (24)
- # spacemacs (7)
- # specter (3)
- # sql (5)
- # yada (5)
hey guys, does somebody here have any experience with extern inference
on the wild? I know that there are some externs for react native but I mean, experience with using only extern inference for releasing a cljs app
I've tried using it, but moved back to regular explicit externs files because I was having problems with defrecords
IIRC.
(My problem surrounding defrecord involved the externs stuff triggering and I couldn't figure out a way to make it happy)
another option is to use goog.object/get and goog.object/getValueByKeys when interacting with React components
@pesterhazy I am currently trying out cljs-oops
. However from what I can understand that library doesnt really solve the problem it just works around it. On the other hand AFAIK the extern inference feature is suppose to solve the externs problems right?