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
I was expecting this library to closely mimic how fetch parses relative paths, so I'm not quite sure if this is a bug or maybe my expectation is wrong. Here's an example:
parse("", "http://foo.com/a/b/c")
Navigates up the hierarchy and produces:
"http://foo.com/a/b"
But I was expecting the path remain unchanged http://foo.com/a/b/c. Here's an example with fetch(''):
Assuming i'm already on http://foo.com/a/b/c
fetch('')
would init a request for "http://foo.com/a/b/c"
Thoughts?
The text was updated successfully, but these errors were encountered:
Hi
I was expecting this library to closely mimic how
fetch
parses relative paths, so I'm not quite sure if this is a bug or maybe my expectation is wrong. Here's an example:But I was expecting the path remain unchanged
http://foo.com/a/b/c
. Here's an example withfetch('')
:Thoughts?
The text was updated successfully, but these errors were encountered: