-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add prev
to UploadsListProvider context value
#143
Comments
@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 |
travis
added a commit
to storacha/w3up
that referenced
this issue
Feb 6, 2023
Per storacha/w3ui#143 we'd like to give clients a way to get the previous page of results rather than the next page. This change introduces a `prev` caveat which, when set to true, will return the page of results preceding `cursor`. I considered calling this `reverse` or `rev` but I think that implies that results will be returned sorted in reverse, which is not the intent.
travis
added a commit
to storacha/w3up
that referenced
this issue
Feb 10, 2023
Per storacha/w3ui#143 we'd like to give clients a way to get the previous page of results rather than the next page. This change introduces a `pre` caveat which, when set to true, will return the page of results preceding `cursor`. I considered calling this `reverse` or `rev` but I think that implies that results will be returned sorted in reverse, which is not the intent. --------- Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>
gobengo
pushed a commit
to storacha/w3up
that referenced
this issue
Apr 11, 2023
Per storacha/w3ui#143 we'd like to give clients a way to get the previous page of results rather than the next page. This change introduces a `pre` caveat which, when set to true, will return the page of results preceding `cursor`. I considered calling this `reverse` or `rev` but I think that implies that results will be returned sorted in reverse, which is not the intent. --------- Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: