This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-13
Channels
- # aleph (3)
- # announcements (2)
- # aws (48)
- # babashka (93)
- # beginners (101)
- # bristol-clojurians (1)
- # cider (3)
- # clj-kondo (17)
- # cljdoc (1)
- # cljsrn (3)
- # clojure (208)
- # clojure-dev (2)
- # clojure-europe (19)
- # clojure-italy (18)
- # clojure-losangeles (16)
- # clojure-nl (8)
- # clojure-spec (21)
- # clojure-sweden (8)
- # clojure-uk (57)
- # clojuredesign-podcast (6)
- # clojurescript (10)
- # code-reviews (6)
- # core-typed (1)
- # cryogen (7)
- # cursive (38)
- # datomic (34)
- # duct (13)
- # emacs (13)
- # fulcro (16)
- # funcool (2)
- # graalvm (1)
- # lambdaisland (5)
- # luminus (8)
- # lumo (1)
- # malli (2)
- # off-topic (12)
- # pathom (9)
- # re-frame (13)
- # reagent (11)
- # ring (3)
- # shadow-cljs (15)
- # sql (19)
- # tools-deps (61)
- # xtdb (23)
Has anyone tried using the react-window package to help with scrolling large data sets. ? I could do pagination too, but was checking out this solution as well.
I’m trying to integrate with the react-navigation library, and I need to create a static method on my component class. It works when I create a plain component with create-react-class and then use gobj/extend to add the static. But I can’t get it working when I use defsc. I know this was possible a long time ago with the defui macro, but how can I do it now with defsc?
as of react 3, adding extra functions to the config map just puts them under :fulcro$options
key on both the instance and the class
whereas before you could actually decorate the class
what happens if you define a class with defsc
then use gobj/extend
to add a static method to it?
looks like that’s what defsc
is doing internally anyway
That’s exactly what I tried, but it didn’t appear to work. I’ll dig into it some more.
So gobj/extend was working, but the error was elsewhere. This library is a real pain to integrate with, but I’m 2/3 of the way there. I have wrappers that work for their AppContainer and Navigators, now just have to get a wrapper working for individual screens, which is a challenge because their Navigator appears to be swallowing all the props I try to pass in. 😤
Yeah, several times. The problem is, it’s more like react-class as a child - it won’t let me pass in a function for individual screens. It wants the component class, and they are creating their own factory - so nowhere to intercept and sneak in props.
Ah, but according to the docs, it looks like the Navigator can take a screenProps
in its props - that’s probably the fix. Trying now.