(142076445) Allow URL.standardized to return an empty string URL #1110
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.
Calling
URL.standardized
on a URL like../../../../
removes the dot segments and produces an empty string.NSURL
allows the empty string, and in the old implementation, this would return aURL
that wraps an empty stringNSURL
.In the new implementation, we ultimately call
URL(string: "")
when initializing this standardized URL, which returnsnil
again after #1103. SinceURL.standardized
returns a non-nilURL
, this would crash when unwrapped.We can allow
URL.standardized
(and other methods that callURLComponents.url
) to return an empty stringURL
as they did previously by usingURL(string:relativeTo:)
instead.