Clojurians Log v2

Well, anyway I'm having a decent amount of luck with react-reveal. It's surprisingly easy. Framer looks cool regardless, thanks for the link!

May be i am missing something here but for me it is just a data provider. So you should be able to insert the library you need to get the data from the server in each resolver ?

Framer motion is open source ! But framer is a another tool from the same company

https://www.framer.com/motion/

i think you should go directly with framer motion as it is a breeze to use and so powerful

@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.

https://hasura.io/

@mikethompson are you using https://github.com/oliyh/re-graph to connect to Hasura?

for large applications I want something like Apollo GraphQL or Relay, to handle sharing and subscribing to queries across components

so the server uses pathom, and the client uses something else to interface with pathom and intelligently cache

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 😞

It is, AFAICT

huh. I wonder how I failed to find this. Error exists between keyboard and chair, apparently. 😛 Thanks a ton!!

I will definitely give Motion a shot, it's definitely more expressive than what I'm hacking on currently.

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.

But one of the dependency component trees just is ignored.

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.

Wonder if there are outstanding issues that could possibly relate.

I’ll dig. Was searching for like “re-render” as the term.

I’ve seen similar behavior when a reagent component is called as a function, rather than in hiccup

not sure if that helps your investigation

I’m using hiccup for sure. I did look closely for that

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}]

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.

@xhh 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.