v0.4.0 release
#67
Merged
v0.4.0 release
#67
Conversation
This file contains hidden or 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
…orest docs: add EternityForest as a contributor for code, doc
Enable listing contents of subfolders on the SAF
Fix subfolder contents listing and `openDocumentFile` API
Add `v0.4.0` changes to `CHANGELOG.md`
…0.4.0 Set package version to `v0.4.0`
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.
0.4.0
Fix the current behavior of
listFilesandopenDocumentFileAPI.Improvements
openDocumentTree(@EternityForest).ACTION_VIEWintent builder throughopenDocumentFileAPI was fixed. So it's now possible to open any file of any kind in third party apps without needing specify the mime type.Breaking changes
DocumentFile.listFiles(Now it's only available globally).buildDocumentUriUsingTreeremoved due high coupling with Android API (Android specific API that are not useful on any other platforms).buildDocumentUriremoved due high coupling with Android API (Android specific API that are not useful on any other platforms).buildTreeDocumentUriremoved due high coupling with Android API (Android specific API that are not useful on any other platforms).getDocumentThumbnailnow receives only theuriparam instead of arootUriand adocumentId.rootUrifield fromQueryMetadatawas removed due API ambiguity: there's no such concept in the Android API and this is not required by it to work well.