Rename list files use case #31
Merged
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
HectorNarvaez
added
Don't merge
HectorNarvaez
requested review from
wilsoncastiblanco,
jdiegoh3,
Anwera64,
hans-hamel and
bardur-encora
Merged
HectorNarvaez
force-pushed
the
state/renameListFilesUseCase
branch
2 times, most recently
from
e213f9b
to
f5ea287
Compare
HectorNarvaez
removed
Don't merge
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.
As the function for get the files list from remote will always receive the parent id, i decided to rename the class GetFilesListWithParentIdUseCase into GetFilesListUseCase. Is less verbose and have the same meaning.
This PR depends on #30, and can see easy diff clicking here