We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm submitting a ... (check one with "x") [X ] feature request
Current behavior: In last version 3.8.0, following this commit f98f90a, DirectoryEntry.nativeURL was removed
Expected behavior: Shouldn't DirectoryEntry.nativeURL be still accessible as it give the native directory path on the device?
For example, when I print a console.log of a root DirectoryEntry, nativeURL is defined:
{"isFile":false,"isDirectory":true,"name":"","fullPath":"/","filesystem":"<FileSystem: cache>","nativeURL":"file:///var/mobile/Containers/Data/Application/3A9F...9FD/Library/Caches/"}
The text was updated successfully, but these errors were encountered:
d0dec7a
cool thx a lot @ihadeed!
Sorry, something went wrong.
No branches or pull requests
I'm submitting a ... (check one with "x")
[X ] feature request
Current behavior:
In last version 3.8.0, following this commit f98f90a, DirectoryEntry.nativeURL was removed
Expected behavior:
Shouldn't DirectoryEntry.nativeURL be still accessible as it give the native directory path on the device?
For example, when I print a console.log of a root DirectoryEntry, nativeURL is defined:
{"isFile":false,"isDirectory":true,"name":"","fullPath":"/","filesystem":"<FileSystem: cache>","nativeURL":"file:///var/mobile/Containers/Data/Application/3A9F...9FD/Library/Caches/"}
The text was updated successfully, but these errors were encountered: