This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-05
Channels
- # announcements (17)
- # aws (1)
- # babashka (68)
- # beginners (88)
- # calva (85)
- # chlorine-clover (10)
- # cider (5)
- # cljsrn (4)
- # clojure (99)
- # clojure-android (1)
- # clojure-denmark (1)
- # clojure-europe (15)
- # clojure-italy (5)
- # clojure-nl (3)
- # clojure-spec (1)
- # clojure-uk (67)
- # clojurescript (44)
- # core-async (44)
- # cryogen (4)
- # cursive (22)
- # data-science (2)
- # datascript (10)
- # datomic (29)
- # duct (11)
- # editors (2)
- # emacs (2)
- # events (1)
- # fulcro (28)
- # ghostwheel (7)
- # graalvm (8)
- # instaparse (6)
- # java (34)
- # jobs (9)
- # jobs-discuss (71)
- # juxt (12)
- # luminus (3)
- # malli (15)
- # meander (9)
- # nrepl (4)
- # off-topic (44)
- # pathom (13)
- # reagent (22)
- # schema (1)
- # shadow-cljs (39)
- # spacemacs (2)
- # test-check (1)
- # tree-sitter (5)
- # xtdb (5)
- # yada (1)
@slawek098 We use re-frame with Hasura/Postgress and it is working out well. Hasura's subscriptions seem to be endlessly useful. We use Hasura's webhooks to callout to perform serverside logic (this logic can be in whatever language you want, including Clojure or Python or whatever) In fact, you can use an approach where saving a record in the database, triggers serverside code, which acts as someone of an effect handler.
Hmm. I'm not sure I describing this well enough. Anyway, key takeaway is that Hasura might be a terrific addition to your architecture, if you use Postgres.
@mikethompson are you using https://github.com/oliyh/re-graph to connect to Hasura?
@U0626CD3J Yes, we use re-graph. i can't say I love it. It feels like the weakest part of the stack. So, I keep threatening to replace it with something better, but then a distraction happens. That's been happening for a year.
hi, I'm trying to understand if it is ok to have reagent-components with multi-arity, but didn't found any info on that š
I have a case where one of my components is not updating. Using a basic re-frame subscription. The value in it is clearly changing and the reaction is firing.
One of the first Iāve seen of this doing nothing special. Standard render fn form-1. No closure situation etc.
Sort of hard to troubleshoot. Thinking Iāll try to look some at the queue stuff in reagent and dig around. I canāt reproduce it in a small example unfortunately. I probably could if I knew the cause, but thatās the problem! Hah.
It initially renders and uses the value too. Itās just a value change doesnāt trigger. If I do something else to affect the component tree it then does update.
Iāve seen similar behavior when a reagent component is called as a function, rather than in hiccup
And I know I gave no solid details. Hah. I appreciate that input. It certainly has been a problem Iāve seen people have before.
This is the most common bug symptom I see with React-based components. I usually fix it by manually putting a key on the component and making sure the key changes whenever the value changes, like this
^{:key (str "my-widget-" value)}
[my-component {:value value}]
@U06CM8C3V thanks for the tip - I overlooked it yesterday - Iāll experiment with this
The tricky part is sometimes itās the element itself that responds to the key, and sometimes itās a parent component. But once you get it right it stays fixed.