Added content_hash to FileMetadata and options to list_folder request #14
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
|
Thanks for this, hopefully it will get merged in soon |
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.
Hi,
A couple of additions for your consideration, please:
Content_hash information allows us to check locally if the file has been changed since the previous upload (using the DropboxContentHasher gem, for example). This PR add this field to FileMetadata.
The list_folder API call has some useful options, e.g. recursing, listing deleted files, etc., so these options have been added into this method.
Optionally, I've cheekily included emacs save files to the .gitignore file. :-)
Thanks,
Jason