I'm a newbie but it seems this is just what I expected from fulcro in previous question on the channel yesterday I won't say if its good or bad but it for sure is an alternative concept. I'm thinking you can implement it in at least 2 way more with different query key or with different rendering optimizer is that so? it seems to me this borrows from redux javascript library am I right?

Hi. I don't believe your question is related to this. If I follow correctly, you are wondering if you always need to pass props to child components, and the answer is yes. This is a fundamental design of fulcro.

What I described is only dealing with derived data which fulcro does not maintain in its indexes, and thus cannot update efficiently without you telling it to (or doing a crude full re-render from root)

hm ok when I saw your post I thought that what you made is something that would work similarly as reducer in react-boilerplate like if something changes in the local database you would have subscription for it that would trigger a rerender which is what reducers do in react-boilerplate I was spending bit of time trying to use query as reducer from react-boilerplate without success I guess with your approach it would be possible. thats one of the things why I asked about props. its just latter that I found out from tutorials how does fulcro deal with this. thanks for reply. I'm still trying to get better grasp of fulcro so I'm not very competent to comment

Ah I see thanks for clarifying! I think it's analogous then yes. It was hard to understand without code examples.

for what I saw in javascript world there are two approaches that compete with fulcro approach when it comes to state management thats reducers approach and rxjs approach of angular where people might chose not to go with redux but use rxjs pipes. fulcro in a way competes with them with its methods and innovating a bit. it for sure is attractive to experiment with all these ideas

I’ve only been using Fulcro for about 4 months so take anything I say with a huge lump of salt! 😄 I’m looking forward (and I know others are too) for a good solution for derived data in Fulcro. Having used some code that tackles these concerns the two key takeaways I have is the solution must not leak (i.e. where you use it must be totally transparent to surrounding code) and it must fit seamlessly with Fulcro’s ‘philosophy’ (for lack of a better word). Caveat, I’ve only just skimmed the readme; but the extra ::rfm/subs key gives me pause for concern. How would you compare your solution to Pathom3's take on derived state (computed graph nodes)? (Caveat I also haven’t looked too deep into Pathom3 yet! 😄 )

This is not my solution, it is non-abstracted re-frame subscriptions https://day8.github.io/re-frame/correcting-a-wrong/

I’m not sure what you mean? (FWIW I know re-frame pretty well so am familiar with subscriptions in general) I think the point I was not making very well is; the query is such a fundamental component of Fulcro that I feel any deviation from it (with the sideband ::subs key) should be thought about very carefully. It seems to me (again, from very little skimming of the website) that Pathom3 gives you derived state that fits in with the Fulcro query in a far more ‘natural’ way? :woman-shrugging:

TBH, in my case a far faster quick fix would be to just use transients for the heavy caclulation part and blindly derive on each render. The JS runtime is pretty fast!

RAD requires multi-root renderer if you’re using SUI plugin, or some controls will not work.

Why do you want just a single person to update? Trying to optimize? I would recommend getting really familiar with Fulcro before trying to do anything fancy.

I'm trying now to follow fulcro tutorial how rendering works and I have trouble reproducing what Mr. Kay did there in the way I tried I hope to do what he did in the video I tried copy pasting the code into rad after cloning rad as is but I guess now it does not work due to rad using another render that behaves differently than the one in tutorial. not sure if one can specify the other renderer I just trying to force the optimized one into it like in the video 🙂 now I'm falling back to code from repository in the video trying to follow step by step until I see it working trying to get my feet wet with the fulcro it looks like a really nice software

it seems I used latest fulcro but ident optimizer is not the default anymore one has to specify it explicitly if one tries to follow tutorials with the latest fulcro if anyone searches for this in google I guess someone will spot this chat

seems reasonable..but have I already messed up and used a non-map as that argument?

query-params is a map, but we’d have to nest it inside another map

i dont believe you’ve pushed a release of this code fwiw, but some may be using it

Ah, if I have not actually released it, then yes, let’s fix it

I think you’re about the only person even aware it exists

yeah i think so as well 😄

https://github.com/fulcrologic/fulcro/pull/476

i can add a follow-up one adding without support, but it’ll require proxying data-fetch ’s elide-query-nodes and elide-ast-nodes to a helper namespace so that mutations can use those as well