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
parse-url 8.x deprecated support for URLs that just start with a / for a local path like /tmp/myrepo. They have to be prefixed with file:// now or you get:
Uncaught Error: URL parsing failed.
I get their rationale for dropping support for that but I wonder if it was intended that git-url-parse lose the same support? I'd like my application depending on git-url-parse to be able to handle any URL that the official git client does and right now git-url-parse throws errors for these URLs that are valid in git configs
Would it make sense for the git-url-parse or git-up projects to contain logic layered above parse-url for handling local paths?
A simple implementation might just be detecting input strings that start with / and prefixing them with file:// automatically before passing to parse-url
The text was updated successfully, but these errors were encountered:
parse-url
8.x deprecated support for URLs that just start with a/
for a local path like/tmp/myrepo
. They have to be prefixed withfile://
now or you get:I get their rationale for dropping support for that but I wonder if it was intended that
git-url-parse
lose the same support? I'd like my application depending ongit-url-parse
to be able to handle any URL that the officialgit
client does and right nowgit-url-parse
throws errors for these URLs that are valid ingit
configsWould it make sense for the
git-url-parse
orgit-up
projects to contain logic layered aboveparse-url
for handling local paths?A simple implementation might just be detecting input strings that start with
/
and prefixing them withfile://
automatically before passing toparse-url
The text was updated successfully, but these errors were encountered: