Download end point refactor #1547
Open
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.
Summary
Following the work done in #1529 this PR refactors the
downloadend-point. The process followed was very similar:This PR enables
files/downloadandfiles/provider/downloadend-points to be able to download the files from the user and provider directory.Details and comments
files/downloadend-point was separated in two:files/downloadnow contains the paths:username/andusername/provider/function. Following the previous development, with the purpose to separate files to be downloaded from functions from the user's root folder.files/provider/downloadto manage the pathprovider/functionso now each function will have its own folder in the provider directory to download the files.