Evert Pot

So the main issue is, how are you going to deal with de-duplicated requests? For example, it's possible to do 2 GET requests, but Ketting will ensure only 1 goes...

The way usePagedCollection works today is that it actually *appends* data from the next pages, facilitating 'infinite scroll' interfaces. However, I think it might also be useful for a non-infinite-scroll...

@ogenodisho yeah a flag is a good way to handle this =)

Makes sense!

Interesting idea. Usually I would recommend to people to try and figure out why they need it (can you invalidate the cache in another way? why does it need to...

Hi Gwen, The normal way to solve this that you use `useCollection`, and for each item (in `items`) that you receive you create a new component that uses the `useResource`...

> When one element changes, the sum must be refreshed. That does make sense. The server-side way to handle this, is if you did a `PUT` request on any of...

This choice was deliberate at the time, because if we change the type to something like this: ```typescript type UseResourceResult = { loading: true, error: undefined, data: undefined, } |...

Thank you!

Seems reasonable!