fix: use URL constructor instead of url.parse() #33

nlf · 2022-02-24T21:20:57Z

BREAKING CHANGE: this removes the (hopefully) unused feature that
arbitrary strings are allowed as URLs in the Request constructor. we now
require that URLs are valid and absolute.

BREAKING CHANGE: this removes the (hopefully) unused feature that arbitrary strings are allowed as URLs in the Request constructor. we now require that URLs are valid and absolute.

lib/index.js

nlf added 2 commits February 24, 2022 13:19

fix: use URL constructor instead of url.parse()

52be9e2

BREAKING CHANGE: this removes the (hopefully) unused feature that arbitrary strings are allowed as URLs in the Request constructor. we now require that URLs are valid and absolute.

fixup! fix: use URL constructor instead of url.parse()

57e64e8

wraithgar reviewed Feb 24, 2022

View reviewed changes

lib/index.js Show resolved Hide resolved

wraithgar approved these changes Feb 24, 2022

View reviewed changes

nlf merged commit f96f3b1 into main Feb 24, 2022

nlf deleted the nlf/no-url-parse branch February 24, 2022 22:44

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: use URL constructor instead of url.parse() #33

fix: use URL constructor instead of url.parse() #33

nlf commented Feb 24, 2022

fix: use URL constructor instead of url.parse() #33

fix: use URL constructor instead of url.parse() #33

Conversation

nlf commented Feb 24, 2022