Update <PrevNextButtons> to fetch less aggressively

[fzaninotto]

Problem

<PrevNextButtons> has to fetch the entire list to determine the previous and next id. This may be costly in network and server time (on the client-side, iven with a list of 1000 items, the time is negligible).

Solution

Check if the previous and next id can't be determined from the cache first, so that users coming from a list page don't need to fetch the entire list of records

Out of scope

When a user reaches the end of the list cache, update the list params in the store to increment or decrement the page.

To Do

• Use <PrevNextButtons /> in the demo
• Allow to specify filterDefaultValues
• Use the cache if possible

[fzaninotto]

I used useQuery instead of useGetList to avoid paying the tax of prepopulating the getOne cache, which can be costly for large lists.