Combining reactive_stores with resources and hydration

[actualwitch]

Hello friends!

I'm looking to switch to leptos from node/react stack and decided to write a small production-like app to see how it works, but trying to combine the patterns in the book in one app seems challenging to me. Here's what I want to achieve:

• a bunch of server functions querying the db
• depending on route, call the necessary functions on server and await all of them before sending to client
• upgrade returned data to signals so that I can trigger refetch on client and have updates shown immediately

Seemingly, Resources are the intended solution for 1 & 2 and I can get them to work with ssr, but then I need to manually upgrade all the data to signals.reactive_stores solve 3, but I can't seem to find an easy solution to initialize them on server based on resources. leptos-query seems like the solution I am looking for, but it doesn't support leptos 0.7. So what is the intended way to approach this?

Thanks in advance.

[gbj]

There are really two separate questions here, I think.

1. How can you have something like a ResourceStore, which combines the server loading features of resources and the field access of stores? This is a good idea and maybe a plan for the future, it just doesn't exist at the moment, sorry.

2. This part:

upgrade returned data to signals so that I can trigger refetch on client and have updates shown immediately

The first half ("upgrade returned data to signals") doesn't follow from the second half ("trigger refetch on client and have updates shown immediately"), although the second half is also confusing to me.

Resources can be mutated like signals, so there is no need to upgrade a resource to a signal to be able to have updates on the client. Resources can also be manually refetched, or invalidated and refetched with their source signal.

Happy to try to help with any of that if you have an example, or to try to give another response if I'm misunderstanding.

[actualwitch]

Sorry, should have been more clear on the 2 - I mean recursively, so update a resource returning vector of data and have each entry be reactive, i.e. what is described in https://book.leptos.dev/view/04b_iteration.html

[gbj]

If you want to do that with a resource then as far as I know, currently the best way to do it would be to make a memo of the current value of each entry (that's Option 3 here) but I can't say I've done much work with examples like this personally.

[actualwitch]

thank you for following up on this! i tried all of the solutions before unsuccessfully and was ready to give up, but tried it again just now and found success after a bit of bruteforcing. to expand further on the problem i was having, without .awaiting on the resource i had hydration mismatches but after combining memoized slices with await it seems to be working (probably sub optimally but still)