[
https://issues.apache.org/jira/browse/CB-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883150#comment-13883150
]
Ian Clelland commented on CB-3413:
----------------------------------
Additionally, regarding the fullPath vs toURL() comments above -- As per spec,
Entry.fullPath is now the filesystem-root-relative path to the file, so a file
which would have previously been (on Android)
{code}
file:///storage/emulated/0/path/to/file.txt
{code}
is now represented by a FileEntry whose {{.toURL()}} method returns
{code}
cdvfile://locahost/persistent/path/to/file.txt
{code}
and whose {{.fullPath}} property is simply
{code}
/path/to/file.txt
{code}
The iOS implementation is identical, except for the exact device-specific file
location.
> Inconsistency in GetFileEntry - uri's vs paths
> ----------------------------------------------
>
> Key: CB-3413
> URL: https://issues.apache.org/jira/browse/CB-3413
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, iOS, Plugin File
> Affects Versions: 2.7.0
> Reporter: Shravan Narayan
> Assignee: Ian Clelland
> Fix For: 3.4.0
>
>
> The getFileEntry in android returs a file: uri "file:///storage/something"
> while the getFileEntry on ios returns a file path "/var/something"...
> It is unclear whether we need to return a file: uri here or a path, but at
> the very least it should be consistent.
> Other platforms will have to be tested to ensure they are consistent with the
> chosen solution as well.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
