Add baseUrl option, rename prefixUrl, and allow leading slashes in input #606
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to improve the flexibility of input URLs and options for resolving them prior to the request.
prefixUrl
is renamed tostartPath
input
before any other processing takes placestartPath
can still be a full URL if needed, however the name is meant to signal its primary use case is a simple base path without a domain, e.g./api
baseUrl
option is addedinput
(including anystartPath
) is resolved against thebaseUrl
according to standard URL resolution rulesbaseUrl
will respect the HTML<base>
tag if present, and is similar to it, except that it only applies to Kyinput
can now be any valid URL, with or without a leading slashstartPath
baseUrl
Possible names for the string that is prepended to
input
startPath
(as is currently implemented here)pathPrefix
prefixPath
rootPath
TODO:
startPath
option