feat: upload server side pagination #1699
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ination. Add removed `after` filtering parameter to the endpoint. Document `sortBy`, `sortOrder`, `after` & `offset` in the swagger docs. Set `Size` param default to 10 from 25.
…size is returned. Add tests for date filtering (before & after) and sorting by date.
…get-upload-pagination
…` endpoint in the API.
…se for get user/uploads to allow for pagination. Renames `Link` to `Next_link` in header to be more descriptive.
…o prevent comparing to message string. Remove .only.
…get-upload-pagination
…get-upload-pagination
…get-upload-pagination
…optimise `sortBy` queries on the `GET user/uploads` endpoint.
…get-upload-pagination
…coding of variables for header links.
|
Closing this PR as it is superseded by #1836 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #1362