`del` method requires fully formed urls
See original GitHub issueThe .del
method only seems to work if you pass a fully qualified url (hostname + path) as the argument.
However, the example in the README seems to operate with just the path (no hostname) in both string argument, and object argument forms.
Should the README documentation be updated to reflect the format that del
is expecting, or should del
be patched to work with path-only urls?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
What is a URL (Uniform Resource Locator)? Definition from ...
A URL (Uniform Resource Locator) is a unique identifier used to locate a resource on the Internet. It is also referred to as...
Read more >HTTP/1.1: Method Definitions
The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI refers to...
Read more ><input type="url"> - HTML: HyperText Markup Language | MDN
By adding the required attribute, only properly-formed URLs are allowed; the input is no longer considered valid when empty.
Read more >Methods for De-identification of PHI - HHS.gov
Two methods to achieve de-identification in accordance with the HIPAA Privacy Rule. The first is the “Expert Determination” method: (b) Implementation ...
Read more >Localized Versions of your Pages | Google Search Central
Each language version must list itself as well as all other language versions. Alternate URLs must be fully-qualified, including the transport ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @ekalinin. Thanks for chiming in.
I’ve reproduced a case here on Runkit. Note: I used the same version of sitemap.js (v1.2.0) as when I reported this issue initially.
It looks like the problem is fixed in the latest codebase, however. Because it’s fixed, I suppose it’s safe to close.
Cool. Thanks @dhritzkiv