[_] fix: endpoint folder/:uuid/content now returns all the content #366
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
|
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.
This is a clone of: #364
The frontend uses the folder/:id endpoint (created in drive-server) to retrieve all content within a folder. This endpoint is utilized in multiple parts of drive-web, making it challenging to deprecate it all at once. Therefore, we are migrating this endpoint.
Issue:
The migrated endpoint currently does not function as expected, returning only 20 files or folders.
Fix:
This PR includes changes to ensure the folder/:folderUuid/content endpoint works as intended, retrieving all the content within a folder without the 20-item limit.