-
-
Notifications
You must be signed in to change notification settings - Fork 33
Unused arguments in DocumentFile.getContent
#107
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
Labels
bug
Something isn't working
Comments
DocumentFile.getContent
You're right, for now you can use: // Workaround <= 0.5.0
uri.getContentAsString(uri); And since it's a breaking change, I'll release a fix in the next major version v0.6.0. Thanks for the issue. |
alexcmgit
added a commit
that referenced
this issue
Nov 7, 2022
alexcmgit
added a commit
that referenced
this issue
Nov 7, 2022
alexcmgit
added a commit
that referenced
this issue
Nov 7, 2022
alexcmgit
added a commit
that referenced
this issue
Nov 7, 2022
alexcmgit
pushed a commit
that referenced
this issue
Nov 7, 2022
|
thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Both
DocumentFile.getContent
andDocumentFile.getContentAsString
demand a parameter calledUri destination
.It is unclear to me why this parameter is needed and it is entirely unused in the code.
Expected behavior
I would assume that neither of those functions would take a parameter, as their location is already available in the properties of the
DocumentFile
itself.shared_storage:
The text was updated successfully, but these errors were encountered: