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
It's possible this is desired and documented behavior, but I couldn't find anything explicitly about it and I was confused. I am using a non-regular protocol with a dash in it, so this should be a faithful reproduction of my test data. I would have expected setting .path() to not require me to pass in the slash.
var a = new URI('example-uri://username:password@127.0.0.1:8080/01234') a.path() "/01234" a.path('01234') a.path(); "01234"
The text was updated successfully, but these errors were encountered:
It's possible this is desired and documented behavior, but I couldn't find anything explicitly about it and I was confused. I am using a non-regular protocol with a dash in it, so this should be a faithful reproduction of my test data. I would have expected setting .path() to not require me to pass in the slash.
var a = new URI('example-uri://username:password@127.0.0.1:8080/01234') a.path() "/01234" a.path('01234') a.path(); "01234"
The text was updated successfully, but these errors were encountered: