To handle something like a React virtualized list that fetches more rows when you scroll past the bottom, I wonder if we need extensions to stripes-connect?
We can keep a local resource, requiredRecords, for the number of records we need and use it as part of the manifest (once STRIPES-54 is in place). Then the query will re-run if that number is updated.
What isn't in stripes-connect though is the logic to handle the fact we only need to fetch the difference. Nor to satisfy a resource with multiple requests---do we forsee a cap on the number of records that can be returned in a single request which could be hit with realistic interactive use?
To handle something like a React virtualized list that fetches more rows when you scroll past the bottom, I wonder if we need extensions to
stripes-connect?We can keep a local resource,
requiredRecords, for the number of records we need and use it as part of the manifest (once STRIPES-54 is in place). Then the query will re-run if that number is updated.What isn't in
stripes-connectthough is the logic to handle the fact we only need to fetch the difference. Nor to satisfy a resource with multiple requests---do we forsee a cap on the number of records that can be returned in a single request which could be hit with realistic interactive use?