-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Url accessor fixes #1589
Url accessor fixes #1589
Conversation
In addition to null, undefined and the empty string are treated as empty (removing the component from the url). The string '#' is treated same as empty values when setting .hash. The string '?' is treated same as empty values when setting .search. Fixes nodejs#1588
Can someone test with restify? All tests pass now with request. I cannot get restify to work at all |
I'll compile and test both again. |
Uninformed LGTM with a question. |
request and restify install fine, except I get the usual gyp 404 with nightly builds, which is unrelated. |
The href cache updating looks fixed too. |
With this patch applied |
|
Unrelated to this PR, but notices this npm test failure:
test: https://github.com/npm/npm/blob/master/test/tap/config-credentials.js The final file is of interest, it deletes a lot of url properties. |
opened #1591 for the |
Also, LGTM on this patch. |
In addition to null, undefined and the empty string are treated as empty (removing the component from the url). The string '#' is treated same as empty values when setting .hash. The string '?' is treated same as empty values when setting .search. PR-URL: #1589 Fixes: #1588 Reviewed-By: Roman Reiss <me@silverwind.io> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Landed in 6687721 |
See #1588
Also includes a commit that fixes href cache invalidation bug as described in #1588 (comment)
cc: @silverwind @domenic @rvagg @chrisdickinson