refactor(stage): create an abstraction for file locations #45
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
nunogoncalves03
changed the title
nunogoncalves03
changed the title
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.
We have recently updated the
Management APIto include new endpoints for managing files in personal and shared spaces. Thus, we would like to update thePython SDKto support these resources as well.Since the methods for stage files and personal/shared space files are quite similar, we would like to refactor the
Python SDKby introducing an abstract class calledFileLocation. This class will initially be implemented byStageand later by the other file spaces.This PR introduces the abstract class and modifies the previously implemented file objects to make them generic for future use with other file spaces.
cc: @ricardoasmarques @kanitsharma