matching the next function that loads the next page of values, we should have a prev function that remembers the cursor of the page before the current one and navigates to it when prev is called.
this should be as simple as remembering the previous cursor in a new useState and using it in a new prev function that looks very similar to next
@alanshaw suggested looking into adding this to the backend, which would be much cleaner on a bunch of levels, so I'm going to dig into how hard that would be
matching the
next
function that loads the next page of values, we should have aprev
function that remembers the cursor of the page before the current one and navigates to it whenprev
is called.this should be as simple as remembering the previous cursor in a new
useState
and using it in a newprev
function that looks very similar tonext