Github user omefire commented on the pull request:
https://github.com/apache/cordova-lib/pull/140#issuecomment-68909782
Using url.parse introduces additional complexity. Especially, Windows paths
are not going to be handled properly: the drive letter gets omitted after
parsing. This leads to more confusion for the user.
Linux/Unix absolute paths would be handled appropriately, but Windows's
wouldn't.
I suggest we remove the file:// prefix and not make config.xml contain urls
for folder paths.
Take the following examples:
1- url.parse('file://D:/Cordova/cordova-lib') =>
{
protocol: 'file:',
slashes: true,
auth: null,
host: 'd',
port: null,
hostname: 'd',
hash: null,
search: null,
query: null,
pathname: '/Cordova/cordova-lib',
path: '/Cordova/cordova-lib',
href: 'file://d/Cordova/cordova-lib'
}
2- url.parse('file://D:\Cordova\cordova-lib') =>
{
protocol: 'file:',
slashes: true,
auth: null,
host: 'd',
port: null,
hostname: 'd',
hash: null,
search: null,
query: null,
pathname: '/:Cordovacordova-lib',
path: '/:Cordovacordova-lib',
href: 'file://d/:Cordovacordova-lib'
}
3- url.parse('file:///Cordova/cordova-lib') =>
{
protocol: 'file:',
slashes: true,
auth: null,
host: '',
port: null,
hostname: '',
hash: null,
search: null,
query: null,
pathname: '/Cordova/cordova-lib',
path: '/Cordova/cordova-lib',
href: 'file:///Cordova/cordova-lib'
}
So, my suggestion is to only support plain filesystem paths for folders in
config.xml.
What do you think ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
