From f566cd5801f081c193d65e73a1b6e7614266c12f Mon Sep 17 00:00:00 2001 From: Jakob Krigovsky Date: Fri, 4 Oct 2019 13:38:34 +0200 Subject: [PATCH] doc: remove misleading paragraph about the Legacy URL API The Legacy URL API is deprecated, see: - https://nodejs.org/api/url.html#url_legacy_url_api - https://nodejs.org/api/deprecations.html# deprecations_dep0116_legacy_url_api PR-URL: https://github.com/nodejs/node/pull/29844 Reviewed-By: James M Snell Reviewed-By: David Carlier Reviewed-By: Trivikram Kamat Reviewed-By: Colin Ihrig Reviewed-By: Anto Aravinth Reviewed-By: Luigi Pinca Reviewed-By: Minwoo Jung --- doc/api/url.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/api/url.md b/doc/api/url.md index 6cb82c71676e3a..3583d3107491b6 100644 --- a/doc/api/url.md +++ b/doc/api/url.md @@ -21,10 +21,6 @@ The `url` module provides two APIs for working with URLs: a legacy API that is Node.js specific, and a newer API that implements the same [WHATWG URL Standard][] used by web browsers. -While the Legacy API has not been deprecated, it is maintained solely for -backwards compatibility with existing applications. New application code -should use the WHATWG API. - A comparison between the WHATWG and Legacy APIs is provided below. Above the URL `'http://user:pass@sub.example.com:8080/p/a/t/h?query=string#hash'`, properties of an object returned by the legacy `url.parse()` are shown. Below it are