This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-11
Channels
- # announcements (7)
- # aws (52)
- # babashka (16)
- # beginners (49)
- # bristol-clojurians (1)
- # calva (2)
- # chlorine-clover (26)
- # cider (6)
- # clara (1)
- # clj-kondo (79)
- # cljfx (15)
- # clojure (82)
- # clojure-berlin (2)
- # clojure-czech (1)
- # clojure-europe (26)
- # clojure-france (91)
- # clojure-germany (48)
- # clojure-nl (7)
- # clojure-norway (99)
- # clojure-uk (54)
- # clojurescript (18)
- # code-reviews (9)
- # data-science (2)
- # datalog (15)
- # datomic (15)
- # depstar (20)
- # emacs (4)
- # events (1)
- # fulcro (30)
- # funcool (1)
- # graphql (1)
- # helix (5)
- # jobs (6)
- # kaocha (12)
- # leiningen (8)
- # luminus (1)
- # malli (13)
- # off-topic (73)
- # pathom (12)
- # portal (11)
- # portland-or (1)
- # re-frame (10)
- # reagent (1)
- # reitit (44)
- # remote-jobs (1)
- # ring (19)
- # shadow-cljs (64)
- # tools-deps (32)
I am a bit lost on how to write best default props. I am using material ui AutoComplete. This has props such as autoComplete which is set to false as default. I would like to invert this and have a different, more specific component but still general, that is called PredictiveInput and it has autoComplete by default set to true. Then, I would like to be able to use ($ PredictiveInput ...) without specifying autoComplete for when it is true, and ($ PredictiveInput {:autoComplete false ...}) when I want to turn it off. The only problem is that in PredictiveInput component I am now writing stuff like ($ AutoComplete {:autoComplete (if (not (nil? auto-complete)) auto-complete true) and because there are several of these options that I would like to configure, it's a bit heavy, too much repetition, hard to see what is going on.