-
Notifications
You must be signed in to change notification settings - Fork 827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow fetching of extraMetadata #1323
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
this would have been nice in v3 |
I have use of this feature too. |
It's definitely a high-value feature, especially for S3 as it holds a lot of useful metadata. |
Feature Request
Scenario / Use-case
Many backends provide more metadata. We currently populate
FileAttributes
with the data, but don't provide a way to access it. While we can't provide interfaces into any of that data in a way that would allow cross adapter use, we can just provide that data. That way when using the Flysystem, if you either know the specific filesystem adapter that will be used, or can use the metadata with a fallback, you can make for a more efficient system. For example, a few systems return the md5sum in the metadata, this can be used to check if a file matches an existing file before updating the file. It's easy enough to check the returned metadata for that field, and if not present, then code a fallback method (it may be more costly to replace the file if it hasn't changed).I believe this would be a BC due to the addition of methods to the interfaces.
Summary
Expose the
extraMetadata
attribute to the end user.The text was updated successfully, but these errors were encountered: