You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The definition of URL or path is not sufficient as "POSIX path" is not formally specified - the link to Wikipedia leads to examples such as hostname:/directorypath/resource but I doubt this is wanted. Furthermore the description of forbidden pathes could be made more clear:
is only / disallowed or every path beginning with /?
is only .hidden disallowed or also other names starting with a dot and/or what about path/to/.hidden/file?
Do avoid having to read the full POSIX specification, how about a formal definition of path such as
any non-empty sequence of bytes except slash and null byte and not starting with a dot is a valid filename
a path is a non-empty sequence of filenames, separated with slash
Participation
I am willing to submit a pull request for this issue.
The text was updated successfully, but these errors were encountered:
What Data Package version are you using?
v2
Describe the Issue
The definition of URL or path is not sufficient as "POSIX path" is not formally specified - the link to Wikipedia leads to examples such as
hostname:/directorypath/resource
but I doubt this is wanted. Furthermore the description of forbidden pathes could be made more clear:/
disallowed or every path beginning with/
?.hidden
disallowed or also other names starting with a dot and/or what aboutpath/to/.hidden/file
?Do avoid having to read the full POSIX specification, how about a formal definition of path such as
Participation
The text was updated successfully, but these errors were encountered: