This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-26
Channels
- # announcements (10)
- # aws (5)
- # babashka (27)
- # beginners (175)
- # boot (1)
- # braveandtrue (2)
- # calva (11)
- # cider (13)
- # clj-kondo (91)
- # cljs-dev (54)
- # cljsrn (20)
- # clojure (164)
- # clojure-gamedev (3)
- # clojure-uk (43)
- # clojurescript (185)
- # core-async (6)
- # core-typed (1)
- # cursive (1)
- # docker (2)
- # emacs (2)
- # figwheel-main (78)
- # fulcro (69)
- # off-topic (20)
- # pathom (30)
- # planck (3)
- # re-frame (6)
- # reagent (70)
- # reitit (26)
- # ring (1)
- # shadow-cljs (120)
- # tools-deps (6)
- # vim (9)
React question; I see this error when I try to split functionality into a subcomponent
VM2781 react_devtools_backend.js:6 Warning: Cannot update a component (`) while rendering a different component (`uix.newgame-dialog/switchgroup`). To locate the bad setState() call inside `uix.newgame-dialog/switchgroup`, follow the stack trace as described in
I appreciate it is telling me that a sub-component cannot start ratttling the cage of a different component's StateHook
but doesn't that significantly impair composability of React components?I know I can work around this by using a global state manager like xframe.core.alpha
but I just want to make sure I've properly understood the issue
Essentially I have a navbar menu item that flicks the visibilit
flag on a Dialog
and they are in completely different components
I suppose I could make them the same component and do the portal thing,
but that would; be proper tail-wagging-the-dog
ah right you are
I was setting default-when-missing values WITHIN the render
its okay to infer default values within render
just not to set them
thank you
oooh interesting, hadn't thought of it that way
oh congrats on your shoutout in https://clojurescript.org/news/2020-04-24-release BTW
I didn't know I was there 😂 I'm not entirely sure why I am, I guess because I was part of the discussions.
Oh cool, so it records local history? Any issues with some of the other functionality like threading or emoji’s/reactions?
Ah ok, was just wondering if over time it recorded the history, so you could scroll back further than slack lets you see if you had it open…
As an aside, anyone got any good ways of grabbing the record symbol? I’m trying to do stuff with protocols/records, and I was using the class, but a single namespace reload in my repl means that my old class is not =
to my new class… I really want to be able to say things like, give me all the record instances that are this record, or conform to this protocol…
I’m beginning to think records/protocols are a bit more trouble than their worth… namespaced maps + multimethods might be better, even with the perf penalty, but it’s not worth doing a rewrite right now…
Maybe I spoke to soon, having an atom with some sim state comprised of records+protocols doesn’t work in repl, loading in the ns just breaks everything :(… Looks like it’s time to rewrite everything with multimethods…
its always a good morning somewhere
(if you travel far enough)