This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-02
Channels
- # aleph (1)
- # architecture (4)
- # beginners (39)
- # boot (12)
- # cider (25)
- # cljs-dev (3)
- # cljsrn (5)
- # clojure (175)
- # clojure-dusseldorf (1)
- # clojure-italy (13)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-spec (52)
- # clojure-uk (110)
- # clojurescript (35)
- # data-science (2)
- # datomic (61)
- # editors (8)
- # emacs (2)
- # fulcro (7)
- # graphql (15)
- # hoplon (1)
- # hyperfiddle (3)
- # jobs (4)
- # jobs-discuss (12)
- # juxt (2)
- # lein-figwheel (6)
- # leiningen (35)
- # off-topic (4)
- # onyx (5)
- # parinfer (1)
- # pedestal (63)
- # re-frame (38)
- # reitit (7)
- # ring-swagger (7)
- # rum (2)
- # shadow-cljs (27)
- # tools-deps (10)
- # uncomplicate (16)
Is there a way to determine when a component is causing “Warning: wrapped-input is changing an uncontrolled input of type undefined to be controlled”?
It's a very common problem, but no, there's no simple way that comes to mind immediately; however, if you write your inputs with ':value (or v "")' you'll generally avoid it
would it make sense to do that in the input wrapper you wrote?
couldn't we check the props for the presence of the key :value
?
Yes, technically, but we already have a ton of macro/function mess in that code…I don’t want to complicate it more for something that has a clear fix and a react warning
yeah that's true